AI Agentsfull-stackmcp-serverprogrammingvibecoding
Installation
# Add to your Claude Code skills
git clone https://github.com/AgiFlow/aicode-toolkit
README.md
AI Code Toolkit
This repo provides:
project and feature scaffolding via templates
file-level design guidance before edits
rule-based review after edits
design-system discovery for frontend work
Why This Exists
As projects scale, conventions in docs like CLAUDE.md, AGENTS.md, and style guides become hard to keep concise and consistently applied by AI agents. This toolkit moves those conventions into reusable template configs (scaffold.yaml, architect.yaml, RULES.yaml) so agents can discover only the relevant guidance when needed.
Quick Start
Requirements:
Node.js >= 18
an MCP-compatible agent such as Claude Code, Cursor, or Gemini CLI
Generates projects and feature boilerplate from templates.
Core tools:
list-boilerplates
use-boilerplate
list-scaffolding-methods
use-scaffold-method
Admin tools:
generate-boilerplate
generate-feature-scaffold
generate-boilerplate-file
architect-mcp
Provides file-specific patterns before edits and reviews changes against RULES.yaml.
Core tools:
get-file-design-pattern
review-code-change
Admin tools:
add-design-pattern
add-rule
style-system
Provides theme, CSS class, and component discovery tools.
Core tools:
list_themes
get_css_classes
get_component_visual
list_shared_components
list_app_components
one-mcp
Provides progressive tool discovery to reduce MCP prompt overhead.
Typical Workflow
Create a Project
User: "Create a Next.js app called dashboard"
Agent:
1. list-boilerplates
2. use-boilerplate
3. Project is generated
Add a Feature
User: "Add a products API route"
Agent:
1. list-scaffolding-methods
2. use-scaffold-method
3. Feature files are generated
Edit a File Safely
User: "Add a products page"
Agent:
1. get-file-design-pattern
2. edit the file using the returned patterns and rules
3. review-code-change
4. fix any violations
Style a Component
User: "Style the button with our theme colors"
Agent:
1. get_css_classes
2. list_shared_components
3. update the component
4. get_component_visual
Defines file-level patterns that should be shown before edits.
patterns:
- name: server-component
description: "Default for page components"
file_patterns:
- "**/app/**/page.tsx"
description: |
- Use async/await for data fetching
- Keep components focused on rendering
- Move business logic to server actions
RULES.yaml
Defines review rules. Rules can be inherited from a global templates/RULES.yaml.
version: '1.0'
template: typescript-lib
rules:
- pattern: src/services/**/*.ts
description: Service Layer Implementation Standards
must_do:
- rule: Create class-based services with single responsibility
codeExample: |-
export class DataProcessorService {
async processData(input: string): Promise<ProcessedData> {
// Implementation
}
}
- rule: Use dependency injection for composability
must_not_do:
- rule: Create static-only utility classes - use functions
codeExample: |-
// ❌ BAD
export class Utils {
static format(s: string) {}
}
// ✅ GOOD
export function format(s: string): string {}
Project Types
Monorepo
Each project references its template in project.json.
The agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
