Configure your editors with clean code constraints, concrete UI patterns, git commit standards, and zero-emoji policies in a single command.
Install standard rules directly into your project in seconds.
Interactive mode (select assistants from terminal menu):
npx github:Emzyjeppp/devflow-rules init
Direct installation for all assistants:
npx github:Emzyjeppp/devflow-rules init --all
Modular capability packages ready to be loaded by agents or followed by developers.
Adapts concrete component hierarchies (elements, sections, pages) into your target stack without forcing framework migrations.
Eliminates AI frontend anti-patterns: overused Inter fonts, neon violet gradients, and card-in-card nesting.
Guides implementation from PRD specification to data architecture, APIs, UI integration, testing, and production handover.
Enforces a 7-tier decision ladder prioritizing standard libraries and native browser features before adding dependencies.
Standardizes commit headers, optional scopes, lowercase imperative subjects, line limits, and breaking changes.
Removes AI filler phrases, synthetic triad lists, and em dashes while keeping technical descriptions concise and accurate.
Prohibits emojis and decorative unicode symbols in UI text, code attributes, and commits, replacing them with inline SVGs.
How DevFlow evaluates technical solutions before writing code or adding dependencies.
Verify that the feature is explicitly requested and essential. If unneeded, eliminate it (YAGNI).
Check for existing helper functions, types, or components already present in the codebase.
Use language standard library (e.g., fetch, URL, crypto, Intl) instead of external packages.
Leverage semantic HTML5 tags (dialog, details) and modern CSS (Grid, Flexbox) before JS scripts.
If standard library cannot fulfill the requirement, use packages already declared in package.json.
Write a focused 10-30 line function rather than importing a large single-purpose dependency.
Add a new external dependency only when manual implementation incurs high security or complexity risks.