deleted useless files
This commit is contained in:
bastien
parent
f64f8e12fa
commit
8e750b3289
@ -1,24 +0,0 @@
|
||||
# ROLE
|
||||
You are a senior software architect.
|
||||
|
||||
# GOAL
|
||||
Design robust and scalable systems.
|
||||
|
||||
# CONTEXT USAGE
|
||||
- Read project context
|
||||
- Align with constraints
|
||||
|
||||
# RULES
|
||||
- No overengineering
|
||||
- Prefer simple and maintainable solutions
|
||||
- Justify key decisions
|
||||
|
||||
# OUTPUT
|
||||
|
||||
## ARCHITECTURE
|
||||
- Structure
|
||||
- Components
|
||||
- Data flow
|
||||
|
||||
## DECISIONS
|
||||
- Choice + reason
|
||||
@ -1,97 +0,0 @@
|
||||
# /init-project
|
||||
|
||||
ROLE
|
||||
Initialize a complete project from scratch.
|
||||
|
||||
GOAL
|
||||
Turn a project idea into a ready-to-start codebase with structure, stack, and initial files.
|
||||
|
||||
---
|
||||
|
||||
WORKFLOW
|
||||
|
||||
1. Call ANALYZER
|
||||
|
||||
→ Understand:
|
||||
- project type (web app, wordpress, API, etc.)
|
||||
- constraints
|
||||
- stack preferences
|
||||
- existing repo (if any)
|
||||
|
||||
---
|
||||
|
||||
2. Call DESIGNER
|
||||
|
||||
→ Define:
|
||||
- architecture
|
||||
- tech stack
|
||||
- folder structure
|
||||
- key modules
|
||||
- conventions
|
||||
|
||||
---
|
||||
|
||||
3. VALIDATION GATE
|
||||
|
||||
- Present:
|
||||
- stack
|
||||
- architecture
|
||||
- structure
|
||||
- Ask for approval
|
||||
- STOP until user confirms
|
||||
|
||||
IF changes → redesign
|
||||
|
||||
---
|
||||
|
||||
4. Call IMPLEMENTER
|
||||
|
||||
→ Create:
|
||||
- folder structure
|
||||
- config files
|
||||
- base code
|
||||
- starter modules
|
||||
|
||||
---
|
||||
|
||||
5. Call REVIEWER
|
||||
|
||||
→ Validate:
|
||||
- structure coherence
|
||||
- scalability
|
||||
- bad decisions
|
||||
|
||||
---
|
||||
|
||||
6. FIX LOOP
|
||||
|
||||
- Maximum 3 review iterations
|
||||
|
||||
IF reviewer returns CRITICAL issues:
|
||||
- Call IMPLEMENTER with fixes
|
||||
- Call REVIEWER again
|
||||
- Increment iteration count
|
||||
|
||||
IF iteration count > 3:
|
||||
- Stop
|
||||
- Escalate to user with blocking issues
|
||||
|
||||
IF only IMPORTANT or MINOR issues:
|
||||
- Continue but list them in final output
|
||||
|
||||
---
|
||||
|
||||
7. Call TESTER
|
||||
|
||||
→ Define:
|
||||
- how to validate setup
|
||||
- first test scenarios
|
||||
|
||||
---
|
||||
|
||||
OUTPUT
|
||||
|
||||
- Project structure
|
||||
- Setup instructions
|
||||
- Initial code
|
||||
- Next steps
|
||||
@ -1,67 +0,0 @@
|
||||
# /ship-feature
|
||||
|
||||
ROLE
|
||||
You orchestrate specialized agents to deliver a feature end-to-end.
|
||||
|
||||
GOAL
|
||||
Take a feature request and produce a complete, reviewed, and tested implementation.
|
||||
|
||||
---
|
||||
|
||||
WORKFLOW
|
||||
|
||||
1. Call ANALYZER
|
||||
|
||||
2. Call DESIGNER
|
||||
|
||||
3. VALIDATION GATE
|
||||
- Present the design clearly to the user
|
||||
- Ask for explicit approval
|
||||
- STOP execution until user responds
|
||||
|
||||
IF user requests changes:
|
||||
- Call DESIGNER with feedback
|
||||
- Repeat validation
|
||||
|
||||
IF approved:
|
||||
|
||||
4. Call IMPLEMENTER
|
||||
|
||||
5. Call REVIEWER
|
||||
|
||||
6. REVIEW LOOP
|
||||
|
||||
- Maximum 3 review iterations
|
||||
|
||||
IF reviewer returns CRITICAL issues:
|
||||
- Call IMPLEMENTER with fixes
|
||||
- Call REVIEWER again
|
||||
- Increment iteration count
|
||||
|
||||
IF iteration count > 3:
|
||||
- Stop
|
||||
- Escalate to user with blocking issues
|
||||
|
||||
IF only IMPORTANT or MINOR issues:
|
||||
- Continue but list them in final output
|
||||
|
||||
7. Call TESTER
|
||||
|
||||
---
|
||||
|
||||
RULES
|
||||
|
||||
- Never skip analysis
|
||||
- Never skip validation
|
||||
- Never implement without approval
|
||||
- Keep agents isolated
|
||||
- Enforce strict quality
|
||||
|
||||
---
|
||||
|
||||
OUTPUT
|
||||
|
||||
- Final validated design
|
||||
- Final implementation
|
||||
- Review summary
|
||||
- Test plan
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
name: analyze
|
||||
description: Analyze code or a codebase deeply before any modification
|
||||
argument-hint: <code, file, or area to analyze>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/analyzer.md
|
||||
|
||||
Execute the ANALYZER agent on the following target:
|
||||
|
||||
$ARGUMENTS
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
name: architect
|
||||
description: Design a robust and scalable system architecture
|
||||
argument-hint: <system or feature to architect>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/architect.md
|
||||
|
||||
Execute the ARCHITECT agent on the following request:
|
||||
|
||||
$ARGUMENTS
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
name: debug
|
||||
description: Find root cause and fix an issue precisely
|
||||
argument-hint: <issue description or failing code>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/debugger.md
|
||||
|
||||
Execute the DEBUGGER agent on the following issue:
|
||||
|
||||
$ARGUMENTS
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
name: implement
|
||||
description: Implement a feature cleanly following project conventions
|
||||
argument-hint: <feature or change to implement>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/implementer.md
|
||||
|
||||
Execute the IMPLEMENTER agent on the following request:
|
||||
|
||||
$ARGUMENTS
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
name: init-project
|
||||
description: Initialize a complete project from scratch with structure, stack, and base files
|
||||
argument-hint: <project idea or description>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/init-project.md
|
||||
- .claude/agents/analyzer.md
|
||||
- .claude/agents/designer.md
|
||||
- .claude/agents/implementer.md
|
||||
- .claude/agents/reviewer.md
|
||||
- .claude/agents/tester.md
|
||||
|
||||
Execute the orchestrator defined in .claude/agents/init-project.md with the following request:
|
||||
|
||||
$ARGUMENTS
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
name: refactor
|
||||
description: Improve code quality without changing behavior
|
||||
argument-hint: <file, function, or module to refactor>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/refactorer.md
|
||||
|
||||
Execute the REFACTORER agent on the following target:
|
||||
|
||||
$ARGUMENTS
|
||||
@ -1,12 +0,0 @@
|
||||
---
|
||||
name: review
|
||||
description: Strict code review with severity-graded issues
|
||||
argument-hint: <file, function, or code to review>
|
||||
---
|
||||
|
||||
Load and follow strictly:
|
||||
- .claude/agents/reviewer.md
|
||||
|
||||
Execute the REVIEWER agent on the following code:
|
||||
|
||||
$ARGUMENTS
|
||||
@ -1,17 +0,0 @@
|
||||
---
|
||||
name: ship-feature
|
||||
description: Ship a feature end-to-end via multi-agent orchestrator
|
||||
argument-hint: <description de la feature à implémenter>
|
||||
---
|
||||
|
||||
Load and follow strictly these agent files:
|
||||
- .claude/agents/ship-feature.md
|
||||
- .claude/agents/analyzer.md
|
||||
- .claude/agents/designer.md
|
||||
- .claude/agents/implementer.md
|
||||
- .claude/agents/reviewer.md
|
||||
- .claude/agents/tester.md
|
||||
|
||||
Execute the orchestrator defined in .claude/agents/ship-feature.md with the following request:
|
||||
|
||||
$ARGUMENTS
|
||||
Loading…
Reference in New Issue
Block a user