npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@relipa/ai-flow-kit

v0.0.5

Published

All-in-one AI Flow Kit for team development with Claude AI - skills, templates, and MCP adapters

Downloads

1,361

Readme

AI Flow Kit

All-in-one package for software development teams using Claude AI.

Developers only need a single command to load ticket context → AI automatically understands the requirements, chooses the workflow, and follows team rules — no long prompts needed, no need to know the templates.


Problems Solved

| Problem | Solution | |--------|-----------| | Multi-step, complex installation | aiflow init — 1 command to set up everything | | Need long prompts for AI to understand | aiflow use PROJ-33 — AI automatically reads from ticket | | Too many templates, not sure which to use | AI auto-detects task type and selects the appropriate skill | | New plugins (superpowers, MCP...) require manual setup | Package auto-sets up hooks, skills, and MCP on init | | Missing investigation / bug reproduction flow | Skill investigate-bug (inherits systematic-debugging) | | Missing impact analysis flow | Skill impact-analysis | | Hard to resume tasks | State Resumption: Unified plan/ docs and context across tools |

Documentation & Guides

[!TIP] After running aiflow init, documentation files are automatically copied to .aiflow/docs/ in your project for easy access.


Overview Flow

┌─────────────────────────────────────────────────────────────────┐
│                        TECH LEAD                                 │
│  npm publish @relipa/ai-flow-kit  →  developer: npm install -g          │
└─────────────────────────────────┬───────────────────────────────┘
                                  │
                    ┌─────────────▼─────────────┐
                    │      aiflow init           │
                    │  --framework spring-boot   │
                    │  --adapter backlog         │
                    └─────────────┬─────────────┘
                                  │ setup
                    ┌─────────────▼──────────────────────────────┐
                    │           Project                           │
                    │  .claude/                                   │
                    │  ├── skills/          ← superpowers + custom│
                    │  ├── hooks/           ← SessionStart hook   │
                    │  └── settings.json    ← hook config         │
                    │  .aiflow/                                   │
                    │  ├── context/         ← ticket context      │
                    │  └── versions/        ← versioned skills    │
                    │  .rules/              ← team rules (java/)  │
                    │  CLAUDE.md            ← framework template  │
                    │  .mcp.json            ← MCP adapter config  │
                    └─────────────┬──────────────────────────────┘
                                  │
               ┌──────────────────▼──────────────────┐
               │          Developer workflow          │
               │                                      │
               │  1. aiflow use PROJ-33                │
               │     └─ Pull title, description,      │
               │        and comments from Backlog     │
               │     └─ Save → .claude/context/       │
               │                                      │
               │  2. claude  (open Claude terminal)    │
               │                                      │
               │  3. "Fix bug PROJ-33"  (1 line)       │
               └──────────────────┬──────────────────┘
                                  │
               ┌──────────────────▼──────────────────┐
               │           Claude AI                  │
               │                                      │
               │  SessionStart hook injected          │
               │  using-superpowers skill             │
               │       ↓                              │
               │  Read CLAUDE.md (spring-boot rules)  │
               │       ↓                              │
               │  Read context/current.json (PROJ-33) │
               │       ↓                              │
               │  Auto-detect: bug-fix task           │
               │       ↓                              │
               │  Invoke investigate-bug skill        │
               │  → inherits systematic-debugging     │
               │  → trace Controller→Service→Repo     │
               │  → git blame to understand history   │
               │  → propose minimal fix               │
               │       ↓                              │
               │  Invoke impact-analysis skill        │
               │  → check breaking changes            │
               └──────────────────┬──────────────────┘
                                  │
               ┌──────────────────▼──────────────────┐
               │          Developer review            │
               │  git diff → test → commit            │
               └──────────────────────────────────────┘

Installation

# Stable version
npm install -g @relipa/ai-flow-kit

# Beta version (recommend for newest features)
npm install -g @relipa/ai-flow-kit@beta

# Uninstall
npm uninstall -g @relipa/ai-flow-kit

Commands

| Command | Description | |---------|-------------| | aiflow init | Setup framework, adapters, and multi-AI rules. | | aiflow use <ticket> | Load ticket context (Backlog/Jira). | | aiflow prompt | Generate tool-optimized prompts (--env cursor). | | aiflow telemetry | Manage telemetry tracking (enable/disable/status). | | aiflow guide | View integrated multi-AI integration guide. |

aiflow init

Initial setup for the project. Run once per project.

# Single framework + adapter
aiflow init --framework spring-boot --adapter backlog

# Multiple frameworks and adapters
aiflow init --framework spring-boot,reactjs --adapter backlog,jira

What gets automatically set up:

  • .claude/skills/ — superpowers skills + team custom skills
  • .claude/hooks/session-start.js — SessionStart hook
  • .claude/settings.json — hook configuration
  • .rules/ — team coding rules (based on framework language)
  • CLAUDE.md — framework-specific AI prompt
  • .mcp.json + Claude Desktop config — MCP adapter
  • .aiflow/credentials.json — save API credentials

Supported Frameworks: spring-boot, laravel, reactjs, nextjs, vue-nuxt

Supported Adapters: backlog, jira, google-sheets, figma


aiflow use <ticket>

Load ticket context into .aiflow/context/current.json.

# Backlog
aiflow use PROJ-33
aiflow use https://mycompany.backlog.com/view/PROJ-33

# Jira
aiflow use PROJ-123

# Default: only load description
aiflow use PROJ-33

# Load with all comments
aiflow use PROJ-33 --with-comments

# Load newest 5 comments
aiflow use PROJ-33 --comments-last 5

# Load comments from index 3 onwards
aiflow use PROJ-33 --comments-from 3

# Manual input
aiflow use --manual

# Save with custom name
aiflow use PROJ-33 --save sprint-42-bug

aiflow doctor

Check if the setup is complete.

aiflow doctor
✓ .claude/skills exists (42 skills)
✓ .rules exists
✓ CLAUDE.md exists
✓ SessionStart hook configured
✓ Version tracking active (v1.0.0)
✨ Everything looks healthy!

aiflow update

Update skills, rules, and templates to the latest version.

aiflow update

aiflow validate <file>

Validate code output against team rules.

aiflow validate src/Payment.java --ruleset strict

aiflow memory

Save/search team knowledge.

aiflow memory save "payment-flow" "Payment flow description..."
aiflow memory search "payment"
aiflow memory list

Available Skills

Custom skills (team-specific)

| Skill | Trigger | Description | |-------|---------|-------| | investigate-bug | "fix bug", "error", "crash" | Investigate bugs via data flow, inherits systematic-debugging | | impact-analysis | "impact scope", "breaking change" | Analyze the impact when changing code | | generate-spec | "new feature", "spec", "design" | Write technical specs, integrates brainstorming | | report-customer | "customer report", "incident" | Write incident reports for Customer Service | | figma-to-component | "figma", "design", "generate component" | Read Figma design → generate React/Next.js/Vue component |

Superpowers skills (upstream, inherited from obra/superpowers)

| Skill | Description | |-------|-------| | systematic-debugging | Core debugging methodology — NO FIX WITHOUT ROOT CAUSE | | brainstorming | Explore requirements before coding | | writing-plans | Create bite-sized implementation plans | | executing-plans | Execute plans with review checkpoints | | test-driven-development | RED→GREEN→REFACTOR | | subagent-driven-development | Dispatch subagents for independent tasks | | requesting-code-review | Review code before merging | | verification-before-completion | Verify before claiming done | | using-git-worktrees | Isolated workspace for feature work | | finishing-a-development-branch | Complete branch and merge options |


Framework Templates

| Framework | Language | Rules applied | |-----------|---------|--------------| | spring-boot | Java 17+ | rules/java/ | | laravel | PHP 8.1+ | rules/php/ | | reactjs | TypeScript | rules/javascript/ | | nextjs | TypeScript | rules/javascript/ | | vue-nuxt | TypeScript | rules/javascript/ |


Project Structure

ai-flow-kit/
├── README.md                        # Main documentation
├── bin/aiflow.js                    # CLI entry
├── docs/
│   ├── common/                      # Published with package
│   │   ├── QUICK_START.md           # Quick start guide
│   │   ├── AIFLOW.md                # Workflow (5 Gates) detail
│   │   ├── CHANGELOG.md             # Version history
│   │   ├── cli-reference.md         # Full CLI reference
│   │   └── workflows/               # Per-task workflow guides
│   └── project/                     # Project template files
│       └── ARCHITECTURE.md          # Architecture doc template
├── scripts/
│   ├── init.js                      # Project initialization
│   ├── update.js                    # Version management
│   ├── doctor.js                    # Health check
│   ├── use.js                       # Context loading (Backlog/Jira)
│   ├── config.js                    # Config system
│   ├── detect.js                    # Task type detection
│   ├── validate.js                  # Code validation
│   ├── memory.js                    # Knowledge management
│   └── hooks/session-start.js       # SessionStart hook (Node.js)
├── custom/
│   ├── skills/                      # Team-specific AI skills
│   ├── rules/java/                  # Java/Spring Boot rules
│   ├── rules/php/                   # PHP/Laravel rules
│   ├── rules/javascript/            # JS/TS rules
│   ├── templates/                   # Framework tool templates
│   ├── prompts/                     # Task prompt templates
│   └── mcp-presets/                 # Backlog/Jira/Sheets config
└── upstream/                        # obra/superpowers (inherited)

Adding new frameworks / adapters

New Framework: create custom/templates/<name>.md + custom/rules/<lang>/

New Adapter: create custom/mcp-presets/<name>.json

Custom skill: create custom/skills/<name>/SKILL.md

Then run aiflow update to apply.


Usage Environments

| Environment | Experience | Notes | |-----------|------------|---------| | Claude Code CLI (claude) | ⭐⭐⭐⭐⭐ | Full auto — skills, hook, automatically loaded context | | Claude Extension (VS Code) | ⭐⭐⭐ | aiflow prompt <type> → copy paste | | Antigravity / Cursor | ⭐⭐⭐ | aiflow prompt <type> → copy paste |


Troubleshooting

aiflow not found:

npm install -g @relipa/ai-flow-kit

Backlog load fails:

aiflow doctor
# Re-setup credentials
aiflow init --adapter backlog

Skills not loading in Claude:

# Ensure init was run outside Claude terminal (session-start hook needs restart)
aiflow doctor

See more: docs/common/troubleshooting.md