
Product
Reachability for Ruby Now in Beta
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.
flow-state-dev
Advanced tools
The fastest way to start a modern web project that both you and Claude Code will love
The fastest way to start a modern web project that both you and Claude Code will love.
Flow State Dev (FSD) is an intelligent project scaffolding tool that creates production-ready web applications with built-in security, comprehensive documentation, and AI-optimized workflows. It's designed to eliminate the friction between human developers and AI coding assistants while ensuring your projects start with security best practices from day one.
fsd upgrade --add-frameworkPerfect for AI-assisted development - Commands demonstrate extended thinking processes and create structured documentation. From quick daily tasks to complex architectural decisions!
fsd init with --memory flagfsd upgrade - Interactive upgrade system with backup and rollback capabilityPerfect for existing projects - Finally, a safe way to add Flow State Dev features to projects you've already started! No more starting over.
/breakdown - Analyze scope and create comprehensive issue breakdowns/epic:breakdown - Break large epics into user stories and technical tasks/feature:plan - Complete feature planning from concept to implementation/analyze:scope - Detailed scope analysis with dependency mappingPerfect for the "looks good, make GitHub issues" workflow - These commands take your high-level ideas and automatically break them down into detailed, trackable GitHub issues with proper labels, milestones, and templates. No more manual analysis and issue creation!
fsd slash "/command"fsd store <name> generates complete Pinia storesfsd supabase start/stop/reset/migrate/seeddocs/ folder with context, guides, API docs, and architecture decisions.claude/ folder with personality, code style, and avoid patternsnpx flow-state-dev init
No installation needed! Just run and create your project
npm install -g flow-state-dev
fsd init
The -g flag installs globally so you can use fsd from anywhere
# Create a SvelteKit project with authentication
fsd init my-app --preset sveltekit-full-stack
# Create a React project with Tailwind
fsd init my-app --preset react-frontend
# Create a Vue project with Vuetify
fsd init my-app --preset vue-full-stack
# Create a minimal project (no framework)
fsd init my-app --preset minimal
# Use specific modules
fsd init my-app --modules sveltekit,better-auth,tailwind
Linux Users: If you get an EACCES permission error, don't use sudo! See our Linux Troubleshooting Guide for safe solutions, or just use
npx(Option 1) to avoid installation issues entirely.
The intelligent setup will guide you through:
$ fsd init my-app
π Repository Analysis
β οΈ PUBLIC repository detected: github.com/user/my-app
π¨ SECURITY WARNING: This is a PUBLIC repository!
Anyone can see your code and any secrets you commit.
π Using placeholder values for security
π Created .env.example with safe templates
π Created security documentation
cd your-project-name
npm install
npm run dev
That's it! Your project is configured and ready to run.
By default, Flow State Dev creates a new subfolder for your project. You'll be asked where to put files:
./my-app/ in current directoryUse flags to skip the prompt:
fsd init my-app --subfolder # Always create subfolder
fsd init my-app --here # Use current directory
You now have a fully configured project with:
fsd upgrade --add-frameworkCLAUDE.md file pre-configured with project info.claude/settings.json with pre-approved commands for Claude Codenpx flow-state-dev init # Create a new project
npx flow-state-dev doctor # Run diagnostics
npx flow-state-dev memory init # Setup Claude memory
npx flow-state-dev labels # Setup GitHub labels
npx flow-state-dev security scan # Scan for exposed secrets
npx flow-state-dev store <name> # Generate a Pinia store
npx flow-state-dev upgrade # Add Flow State Dev features to existing projects
# Project Creation
fsd init # Create a new project (interactive)
fsd init --no-interactive # Skip interactive setup
fsd init --here # Use current directory
fsd init --subfolder # Create in subfolder (default)
# Local Development Setup
fsd setup-local # Install Docker & Supabase CLI
fsd supabase init # Initialize Supabase in project
fsd supabase start # Start local Supabase
fsd supabase stop # Stop local Supabase
fsd supabase reset # Reset database
fsd supabase migrate # Run migrations
fsd supabase seed # Seed database
fsd supabase status # Check status
# Security Tools
fsd security scan # Scan project for exposed secrets
fsd security check # Check repository security status
fsd security setup # Configure security tools
# GitHub Integration
fsd labels # Interactive label setup (choose collection)
fsd labels create # Create labels with options
fsd labels list # Show available label collections
fsd labels export # Export current repo labels
# Development Tools
fsd doctor # Run diagnostics on your project
fsd doctor --fix # Auto-fix common issues
# Code Generation
fsd store <name> # Generate a new Pinia store
fsd store user --supabase # Generate Supabase-connected store
fsd store auth --auth # Generate authentication store
fsd store ui --minimal # Generate minimal store
# Claude Memory Management
fsd memory init # Create your Claude Code memory file
fsd memory show # Display your memory file
fsd memory edit # Edit memory file in your editor
fsd memory validate # Validate memory structure
fsd memory fix # Auto-fix memory issues
# Analysis & Planning Commands
fsd slash "/breakdown --scope 'feature description'" # Analyze and create issues
fsd slash "/epic:breakdown --epic 'epic description'" # Break epic into stories
fsd slash "/feature:plan --feature 'feature' --complexity medium" # Feature planning
fsd slash "/analyze:scope --requirements 'requirements'" # Detailed scope analysis
# Examples with issue creation
fsd slash "/breakdown --scope 'user auth system' --create-issues --milestone 'v2.0'"
fsd slash "/epic:breakdown --epic 'dashboard redesign' --create-issues --assignee johndoe"
# Quick Action Commands
fsd slash "/build" # Run project build command
fsd slash "/test --coverage" # Run tests with coverage report
fsd slash "/lint --fix" # Run linter with auto-fix
fsd slash "/typecheck" # Run TypeScript type checking
fsd slash "/status" # Enhanced git status with categorization
fsd slash "/commit" # Interactive conventional commit
fsd slash "/push" # Push to current branch
# Extended Thinking Commands (Deep Analysis)
fsd slash "/plan --topic 'feature architecture' --create-adr" # Comprehensive planning with ADR
fsd slash "/investigate --question 'performance bottlenecks'" # Multi-source research
fsd slash "/decide --decision 'database choice' --alternatives 3" # Decision analysis with ADR
fsd slash "/estimate --work 'API refactoring' --method story-points" # Complex estimation
fsd slash "/debug:strategy --problem 'memory leak' --urgency high" # Systematic debugging
fsd slash "/research --topic 'microservices patterns'" # Deep research analysis
# Project Upgrade & Retrofit System
fsd upgrade # Safely add Flow State Dev features to existing projects
fsd upgrade --preview # Preview changes without applying them
fsd upgrade --features "Documentation,Security" # Apply specific features
fsd upgrade --list-backups # Show available backups
fsd upgrade --rollback backup-2025-01-23-14-30-15 # Rollback to backup
# Help
fsd help # Show all commands
Flow State Dev includes a comprehensive slash command system with 67+ commands across 10 categories. All commands use a modular architecture where each command is a separate module, enabling better performance, maintainability, and extensibility.
| Category | Commands | Description |
|---|---|---|
| Quick Action | 14 | Daily workflow automation (build, test, git operations) |
| Analysis & Planning | 10 | Project analysis and issue creation |
| Workflow Automation | 8 | CI/CD and deployment management |
| Sprint Management | 6 | Agile sprint planning and tracking |
| Estimation | 6 | Story point estimation and capacity planning |
| Extended Thinking | 5 | Deep analysis with AI-style thinking |
| Project Management | 5 | Issues, milestones, and labels |
| Issue Operations | 5 | Bulk operations and dependency analysis |
| Analysis | 5 | Code metrics and quality analysis |
| Utility | 3 | Help, sync, and cleanup commands |
# Quick daily commands with aliases
fsd slash "/b" # Build (alias for /build)
fsd slash "/t" # Test (alias for /test)
fsd slash "/l --fix" # Lint with fix (alias for /lint)
# Sprint management
fsd slash "/sprint:plan --weeks 2 --capacity 40"
fsd slash "/sprint:review --milestone 'Sprint 5'"
# Planning and analysis
fsd slash "/breakdown 'User authentication system' --create-issues"
fsd slash "/epic:breakdown 'Dashboard redesign' --milestone v2.0"
# Extended thinking commands
fsd slash "/plan 'API architecture' --create-adr"
fsd slash "/decide 'Database: PostgreSQL vs MongoDB'"
fsd slash "/alternatives 'State management for React'"
For a complete list of commands, run:
fsd slash "/help"
my-app/
βββ src/
β βββ components/ # Reusable Vue components
β βββ composables/ # Composition API utilities
β βββ router/ # Route definitions
β βββ stores/ # Pinia stores
β βββ services/ # API services (Supabase)
β βββ views/ # Page components
β βββ App.vue # Root component
β βββ main.js # App entry point
βββ docs/ # π Comprehensive documentation
β βββ context/ # Project context for AI & humans
β βββ guides/ # How-to guides
β βββ api/ # API documentation
β βββ architecture/ # Technical decisions
β βββ SECURITY.md # π Security best practices
βββ .claude/ # π€ AI-specific context files
β βββ personality.md # How AI should interact
β βββ code-style.md # Coding preferences
β βββ avoid.md # Anti-patterns to avoid
βββ .security/ # π‘οΈ Security configuration
β βββ secret-patterns.json # Secret detection patterns
βββ .githooks/ # πͺ Git hooks for security
β βββ pre-commit # Automatic secret scanning
βββ public/ # Static assets
βββ .env.example # Environment template (safe to commit)
βββ .gitignore # Enhanced with 60+ security patterns
βββ CLAUDE.md # AI assistant instructions
βββ README.md # Your project docs
Flow State Dev automatically adapts to your repository's security context:
.env.example with safe templates.env files for immediate usefsd security scan commandfsd security scan # Scan entire project
fsd security scan --verbose # Show detailed results
Detects:
fsd security check
Shows:
fsd security setup
Creates:
After creating your GitHub repository:
cd my-awesome-app
fsd labels
This will create a comprehensive set of labels for better issue tracking:
planning, in-progress, review, done, blockedcritical, high, medium, lowtiny, small, medium, large, xlargeSee docs/LABELS.md for complete label usage guidelines.
Flow State Dev includes tools to help you create and manage your Claude Code user memory file:
fsd memory init
This creates a personalized memory file at ~/.claude/CLAUDE.md with:
fsd memory show # Display your current memory file
fsd memory edit # Open memory file in your editor
fsd memory import # Import from existing memory files
fsd memory validate # Validate memory file structure
fsd memory fix # Auto-fix common issues
Memory files help Claude Code understand your preferences across all projects:
Flow State Dev creates multiple files to optimize AI assistance:
Claude Code automatically understands:
Just open your project in Claude Code and start building securely!
Don't want to install globally? Use npx to run Flow State Dev directly:
# Create a new project
npx flow-state-dev init my-app
# Run diagnostics
npx flow-state-dev doctor
# Set up GitHub labels
npx flow-state-dev labels
# Create memory file
npx flow-state-dev memory init
Benefits of using npx:
If Flow State Dev isn't working, run our diagnostic tool:
curl -s https://raw.githubusercontent.com/jezweb/flow-state-dev/main/debug/diagnose.sh | bash
This will analyze your system and provide specific fix recommendations.
Recommended: Use npx to avoid installation issues entirely:
npx flow-state-dev init
If you prefer global installation and encounter permission errors:
# On macOS/Linux, you might need sudo
sudo npm install -g flow-state-dev
# Or configure npm to use a different directory
npm config set prefix ~/.npm-global
export PATH=~/.npm-global/bin:$PATH
If fsd command is not found after global installation:
Quick Solution: Use npx instead
npx flow-state-dev init
Or fix your PATH:
npm bin -g$(npm bin -g)/fsdLinux Users: See our comprehensive Linux Troubleshooting Guide for detailed PATH configuration instructions.
If you see "GitHub CLI not installed" warnings:
gh auth loginfsd labelsFlow State Dev auto-fixes project names:
fsd init my-project creates ./my-project/ subfoldermy-project/ folder and it's empty, Flow State Dev will offer to use itFlow State Dev uses a plugin-based architecture for project initialization:
See docs/MODULAR_ONBOARDING.md for creating custom steps.
Comprehensive label system with:
See docs/GITHUB_PROJECT_MANAGEMENT.md for workflows.
Flow State Dev includes comprehensive security documentation to help you build secure applications:
MIT Β© Jezweb
Flow State Dev believes that security should be built-in, not bolted-on. Every project starts with:
We make it nearly impossible to accidentally expose secrets while maintaining excellent developer experience.
Made with β€οΈ in Newcastle, Australia by Jez
FAQs
The fastest way to start a modern web project that both you and Claude Code will love
We found that flow-state-dev demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago.Β It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Product
Reachability analysis for Ruby is now in beta, helping teams identify which vulnerabilities are truly exploitable in their applications.

Research
/Security News
Malicious npm packages use Adspect cloaking and fake CAPTCHAs to fingerprint visitors and redirect victims to crypto-themed scam sites.

Security News
Recent coverage mislabels the latest TEA protocol spam as a worm. Hereβs whatβs actually happening.