ateschh-kit 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/rules/01-identity.md +32 -0
- package/.claude/rules/02-language.md +21 -0
- package/.claude/rules/03-quality.md +39 -0
- package/.claude/rules/04-completion-lock.md +38 -0
- package/.claude/rules/05-state-management.md +48 -0
- package/.claude/rules/06-requirements-lock.md +69 -0
- package/.claude/rules/07-token-management.md +56 -0
- package/.claude/settings.local.json +13 -0
- package/ARCHITECTURE.md +222 -0
- package/CHANGELOG.md +74 -0
- package/CLAUDE.md +154 -0
- package/CONTRIBUTING.md +53 -0
- package/LICENSE +21 -0
- package/README.md +145 -0
- package/README.tr.md +145 -0
- package/agents/_TEMPLATE.md +59 -0
- package/agents/architect.md +117 -0
- package/agents/coder.md +90 -0
- package/agents/debugger.md +96 -0
- package/agents/deployer.md +123 -0
- package/agents/designer.md +154 -0
- package/agents/idea-analyst.md +92 -0
- package/agents/market-researcher.md +88 -0
- package/agents/requirements-expert.md +80 -0
- package/agents/tester.md +102 -0
- package/bin/install.js +142 -0
- package/package.json +46 -0
- package/skills/architecture-design/SKILL.md +92 -0
- package/skills/context-management/SKILL.md +92 -0
- package/skills/fix-bugs/SKILL.md +67 -0
- package/skills/idea-analysis/SKILL.md +71 -0
- package/skills/market-research/SKILL.md +70 -0
- package/skills/publish/SKILL.md +80 -0
- package/skills/requirements-lock/SKILL.md +75 -0
- package/skills/run-tests/SKILL.md +70 -0
- package/skills/write-code/SKILL.md +92 -0
- package/templates/project/DECISIONS.md +24 -0
- package/templates/project/DESIGN.md +141 -0
- package/templates/project/PLAN.md +63 -0
- package/templates/project/REQUIREMENTS.md +46 -0
- package/templates/project/STATE.md +94 -0
- package/templates/project/STRUCTURE.md +89 -0
- package/workflows/_TEMPLATE.md +44 -0
- package/workflows/brainstorm.md +69 -0
- package/workflows/build.md +92 -0
- package/workflows/deploy.md +85 -0
- package/workflows/design.md +84 -0
- package/workflows/finish.md +90 -0
- package/workflows/map-codebase.md +136 -0
- package/workflows/new-project.md +96 -0
- package/workflows/next.md +79 -0
- package/workflows/quick.md +82 -0
- package/workflows/requirements.md +85 -0
- package/workflows/resume.md +55 -0
- package/workflows/save.md +111 -0
- package/workflows/settings.md +92 -0
- package/workflows/status.md +67 -0
- package/workflows/test.md +105 -0
package/CLAUDE.md
ADDED
|
@@ -0,0 +1,154 @@
|
|
|
1
|
+
# ATESCHH KIT — AI Development System
|
|
2
|
+
|
|
3
|
+
## Identity
|
|
4
|
+
|
|
5
|
+
You are an AI software development assistant.
|
|
6
|
+
Make technical decisions. Explain your choices clearly.
|
|
7
|
+
You build — you don't tell the user to build.
|
|
8
|
+
|
|
9
|
+
Rules: `.claude/rules/` (auto-loaded)
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## Session Start Protocol
|
|
14
|
+
|
|
15
|
+
On every new session, FIRST:
|
|
16
|
+
|
|
17
|
+
1. Read `.state/ACTIVE-PROJECT.md`
|
|
18
|
+
2. If active project exists → read `projects/{name}/STATE.md`
|
|
19
|
+
3. Give user a 3-line summary:
|
|
20
|
+
- "📁 Active project: {name}"
|
|
21
|
+
- "✅ Last completed: {task}"
|
|
22
|
+
- "➡️ Next up: {task}"
|
|
23
|
+
|
|
24
|
+
If no active project:
|
|
25
|
+
> "No active project. Use `/new-project` to start or `/resume` to return to an existing one."
|
|
26
|
+
|
|
27
|
+
---
|
|
28
|
+
|
|
29
|
+
## Slash Commands
|
|
30
|
+
|
|
31
|
+
| Command | What it does | Workflow |
|
|
32
|
+
|---------|-------------|---------|
|
|
33
|
+
| `/new-project` | Start a new project | workflows/new-project.md |
|
|
34
|
+
| `/resume` | Continue where you left off | workflows/resume.md |
|
|
35
|
+
| `/brainstorm` | Idea analysis + market research | workflows/brainstorm.md |
|
|
36
|
+
| `/requirements` | Define and lock tech stack | workflows/requirements.md |
|
|
37
|
+
| `/design` | Pages + UI design | workflows/design.md |
|
|
38
|
+
| `/build` | Write page/module code | workflows/build.md |
|
|
39
|
+
| `/test` | Test + fix bugs | workflows/test.md |
|
|
40
|
+
| `/deploy` | Deploy to production | workflows/deploy.md |
|
|
41
|
+
| `/status` | Progress report | workflows/status.md |
|
|
42
|
+
| `/save` | Save context (cross-platform) | workflows/save.md |
|
|
43
|
+
| `/finish` | Complete and archive project | workflows/finish.md |
|
|
44
|
+
| `/next` | Auto-detect and run next step | workflows/next.md |
|
|
45
|
+
| `/quick` | Ad-hoc task without full pipeline | workflows/quick.md |
|
|
46
|
+
| `/map-codebase` | Analyze existing codebase | workflows/map-codebase.md |
|
|
47
|
+
| `/settings` | View/edit configuration | workflows/settings.md |
|
|
48
|
+
|
|
49
|
+
When a command is run, read the corresponding workflow file and follow its steps.
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
## Project Phases
|
|
54
|
+
|
|
55
|
+
```
|
|
56
|
+
1. /brainstorm → Idea analysis + market research
|
|
57
|
+
2. /requirements → Tech stack locked
|
|
58
|
+
3. /design → Pages + design locked
|
|
59
|
+
4. /build → Build page by page (iterative)
|
|
60
|
+
5. /test → Test + fix bugs
|
|
61
|
+
6. /deploy → Go live
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## Golden Rules (Immutable)
|
|
67
|
+
|
|
68
|
+
1. **ONE PROJECT**: Only one active project at a time
|
|
69
|
+
2. **PLAN FIRST**: Approve PLAN.md before writing code
|
|
70
|
+
3. **REQUIREMENTS LOCK**: Libraries in REQUIREMENTS.md cannot be changed
|
|
71
|
+
4. **SMALL STEPS**: Each task is max 1 hour of work
|
|
72
|
+
5. **SAVE**: Update STATE.md after every task
|
|
73
|
+
6. **SHOW**: Show the result of every action to the user
|
|
74
|
+
7. **BACKLOG**: New ideas go to BACKLOG.md — not now
|
|
75
|
+
|
|
76
|
+
---
|
|
77
|
+
|
|
78
|
+
## Agent System
|
|
79
|
+
|
|
80
|
+
Use specialist agents for complex tasks.
|
|
81
|
+
Agent definitions: `agents/` folder.
|
|
82
|
+
|
|
83
|
+
| Agent | Role | Triggered by |
|
|
84
|
+
|-------|------|-------------|
|
|
85
|
+
| idea-analyst | Analyzes idea with Socratic method | /brainstorm |
|
|
86
|
+
| market-researcher | Competitor and market research | /brainstorm |
|
|
87
|
+
| requirements-expert | Selects and locks tech stack | /requirements |
|
|
88
|
+
| architect | Page structure and features | /design |
|
|
89
|
+
| designer | Colors, fonts, UI system | /design |
|
|
90
|
+
| coder | Implements code | /build |
|
|
91
|
+
| tester | Writes and runs tests | /test |
|
|
92
|
+
| deployer | Deploys to production | /deploy |
|
|
93
|
+
| debugger | Finds and fixes bugs | /test, /build |
|
|
94
|
+
|
|
95
|
+
**Auto-detection**: The system automatically selects the best specialist based on your request. You don't need to mention agent names explicitly.
|
|
96
|
+
|
|
97
|
+
---
|
|
98
|
+
|
|
99
|
+
## Skill System
|
|
100
|
+
|
|
101
|
+
Reusable atomic tasks: `skills/`
|
|
102
|
+
|
|
103
|
+
| Skill | Role |
|
|
104
|
+
|-------|------|
|
|
105
|
+
| idea-analysis | 5-question idea analysis |
|
|
106
|
+
| market-research | 3-5 competitor research |
|
|
107
|
+
| requirements-lock | Write stack decisions to REQUIREMENTS.md |
|
|
108
|
+
| architecture-design | Create STRUCTURE.md + DESIGN.md |
|
|
109
|
+
| write-code | Implement a PLAN.md task |
|
|
110
|
+
| run-tests | L1-L4 validation |
|
|
111
|
+
| fix-bugs | Bug detection + fix |
|
|
112
|
+
| publish | Deploy via MCP |
|
|
113
|
+
| context-management | Save/load/sync session |
|
|
114
|
+
|
|
115
|
+
---
|
|
116
|
+
|
|
117
|
+
## Quality Levels
|
|
118
|
+
|
|
119
|
+
| Level | Check | Required |
|
|
120
|
+
|-------|-------|---------|
|
|
121
|
+
| L1 | Syntax | Always |
|
|
122
|
+
| L2 | Functionality | Always |
|
|
123
|
+
| L3 | Integration | At /test |
|
|
124
|
+
| L4 | Quality | Before /deploy |
|
|
125
|
+
|
|
126
|
+
**Do not proceed to the next task without passing L2.**
|
|
127
|
+
|
|
128
|
+
---
|
|
129
|
+
|
|
130
|
+
## Cross-Platform Usage (Claude Code ↔ Antigravity)
|
|
131
|
+
|
|
132
|
+
When switching platforms:
|
|
133
|
+
1. On current platform: `/save`
|
|
134
|
+
2. On new platform: open the ATESCHH KIT directory
|
|
135
|
+
3. MEMORY.md is auto-loaded
|
|
136
|
+
4. Type `/resume` → continue where you left off
|
|
137
|
+
|
|
138
|
+
---
|
|
139
|
+
|
|
140
|
+
## File System
|
|
141
|
+
|
|
142
|
+
```
|
|
143
|
+
ATESCHH-KIT/
|
|
144
|
+
├── CLAUDE.md ← This file
|
|
145
|
+
├── .claude/rules/ ← Auto-loaded rules
|
|
146
|
+
├── agents/ ← Agent definitions
|
|
147
|
+
├── skills/ ← Skill definitions
|
|
148
|
+
├── workflows/ ← Slash command logic
|
|
149
|
+
├── context-agent/ ← Context management
|
|
150
|
+
├── .state/ ← System state (gitignored)
|
|
151
|
+
├── templates/ ← Project templates
|
|
152
|
+
├── projects/ ← Active projects (gitignored)
|
|
153
|
+
└── archive/ ← Completed projects (gitignored)
|
|
154
|
+
```
|
package/CONTRIBUTING.md
ADDED
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
# Contributing to ateschh-kit
|
|
2
|
+
|
|
3
|
+
Thank you for your interest in contributing!
|
|
4
|
+
|
|
5
|
+
## Ways to Contribute
|
|
6
|
+
|
|
7
|
+
- **Bug reports**: Open an issue describing the behavior and expected behavior
|
|
8
|
+
- **New workflows**: Add a new slash command in `workflows/`
|
|
9
|
+
- **New agents**: Add a specialist agent in `agents/`
|
|
10
|
+
- **New skills**: Add a reusable skill in `skills/`
|
|
11
|
+
- **Documentation**: Improve or translate README files
|
|
12
|
+
- **Stack support**: Add deployment playbooks for new platforms
|
|
13
|
+
|
|
14
|
+
## Guidelines
|
|
15
|
+
|
|
16
|
+
### Adding a Workflow
|
|
17
|
+
|
|
18
|
+
1. Copy `workflows/_TEMPLATE.md`
|
|
19
|
+
2. Fill in all sections
|
|
20
|
+
3. Add the command to `CLAUDE.md` command table
|
|
21
|
+
4. Test it with a real project
|
|
22
|
+
|
|
23
|
+
### Adding an Agent
|
|
24
|
+
|
|
25
|
+
1. Copy `agents/_TEMPLATE.md`
|
|
26
|
+
2. Define: role, process, output format, rules
|
|
27
|
+
3. Reference it from the appropriate workflow
|
|
28
|
+
4. Document which skill(s) it uses
|
|
29
|
+
|
|
30
|
+
### Adding a Skill
|
|
31
|
+
|
|
32
|
+
1. Create `skills/{name}/SKILL.md`
|
|
33
|
+
2. Keep it atomic — one skill, one responsibility
|
|
34
|
+
3. Document: purpose, steps, output template
|
|
35
|
+
|
|
36
|
+
## Principles
|
|
37
|
+
|
|
38
|
+
- **Stay thin**: Orchestrators coordinate. Agents and skills do the work.
|
|
39
|
+
- **Explicit over implicit**: Every rule, every constraint, every output format should be written down.
|
|
40
|
+
- **English only**: All system files are in English. Translations live in README.{lang}.md files.
|
|
41
|
+
- **No personal references**: All content must work for any user.
|
|
42
|
+
|
|
43
|
+
## Pull Request Process
|
|
44
|
+
|
|
45
|
+
1. Fork the repository
|
|
46
|
+
2. Create a branch: `git checkout -b feature/your-feature`
|
|
47
|
+
3. Make your changes
|
|
48
|
+
4. Test with at least one real project
|
|
49
|
+
5. Submit a PR with a clear description
|
|
50
|
+
|
|
51
|
+
## License
|
|
52
|
+
|
|
53
|
+
By contributing, you agree that your contributions will be licensed under the MIT License.
|
package/LICENSE
ADDED
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 ateschh-kit contributors
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|
package/README.md
ADDED
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
# ateschh-kit
|
|
2
|
+
|
|
3
|
+
> A structured AI development system for Claude Code and Antigravity.
|
|
4
|
+
> Goes from idea to deployment without context rot or project abandonment.
|
|
5
|
+
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
## Install
|
|
9
|
+
|
|
10
|
+
```bash
|
|
11
|
+
npx ateschh-kit
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
That's it. The system is now installed in your current directory.
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
## What This Is
|
|
19
|
+
|
|
20
|
+
A structured workflow system that guides AI agents through the full software development lifecycle:
|
|
21
|
+
|
|
22
|
+
```
|
|
23
|
+
/brainstorm → /requirements → /design → /build → /test → /deploy
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Each phase is gated. You can't accidentally skip from brainstorm straight to coding.
|
|
27
|
+
|
|
28
|
+
## Why It Works
|
|
29
|
+
|
|
30
|
+
| Problem | Solution |
|
|
31
|
+
|---------|---------|
|
|
32
|
+
| AI forgets context between sessions | `/save` + `/resume` — works across Claude Code and Antigravity |
|
|
33
|
+
| Mid-project "let's switch frameworks" | REQUIREMENTS.md is locked after approval |
|
|
34
|
+
| Scope creep | New ideas go to BACKLOG.md — not now |
|
|
35
|
+
| Project abandonment | STATE.md always knows what's next |
|
|
36
|
+
| "Just fix this one thing" rabbit holes | `/quick` for ad-hoc tasks, `/next` for auto-pilot |
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## Commands
|
|
41
|
+
|
|
42
|
+
| Command | What it does |
|
|
43
|
+
|---------|-------------|
|
|
44
|
+
| `/new-project` | Start a new project |
|
|
45
|
+
| `/brainstorm` | Analyze your idea + research the market |
|
|
46
|
+
| `/requirements` | Select and lock the tech stack |
|
|
47
|
+
| `/design` | Define pages, features, and visual system |
|
|
48
|
+
| `/build` | Implement one task from the plan |
|
|
49
|
+
| `/test` | Run L1–L4 quality checks |
|
|
50
|
+
| `/deploy` | Deploy to production |
|
|
51
|
+
| `/status` | See where you are |
|
|
52
|
+
| `/save` | Save context (cross-platform) |
|
|
53
|
+
| `/resume` | Continue from last session |
|
|
54
|
+
| `/next` | Auto-detect and run the right next step |
|
|
55
|
+
| `/quick` | Ad-hoc task without the full pipeline |
|
|
56
|
+
| `/map-codebase` | Analyze an existing codebase |
|
|
57
|
+
| `/settings` | View/edit configuration |
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
## How to Use
|
|
62
|
+
|
|
63
|
+
**Starting a new project:**
|
|
64
|
+
```
|
|
65
|
+
/new-project
|
|
66
|
+
/brainstorm ← describe your idea
|
|
67
|
+
/requirements
|
|
68
|
+
/design
|
|
69
|
+
/build ← repeat until done
|
|
70
|
+
/test
|
|
71
|
+
/deploy
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
**Returning to a project:**
|
|
75
|
+
```
|
|
76
|
+
/resume
|
|
77
|
+
# or
|
|
78
|
+
/next ← automatically detects where you left off
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
**Working on an existing codebase:**
|
|
82
|
+
```
|
|
83
|
+
/map-codebase
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
|
|
88
|
+
## What's Inside
|
|
89
|
+
|
|
90
|
+
```
|
|
91
|
+
ateschh-kit/
|
|
92
|
+
├── CLAUDE.md ← Main orchestration file
|
|
93
|
+
├── .claude/rules/ ← 7 auto-loaded behavioral rules
|
|
94
|
+
├── agents/ ← 9 specialist agents
|
|
95
|
+
├── skills/ ← 9 reusable atomic skills
|
|
96
|
+
├── workflows/ ← 15 slash-command workflows
|
|
97
|
+
├── templates/ ← Project file templates
|
|
98
|
+
└── context-agent/ ← Context management system
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
103
|
+
## Supported Platforms
|
|
104
|
+
|
|
105
|
+
| Platform | Status |
|
|
106
|
+
|----------|--------|
|
|
107
|
+
| Claude Code | ✅ Full support |
|
|
108
|
+
| Antigravity | ✅ Full support |
|
|
109
|
+
| Cursor | ✅ Works (agents folder) |
|
|
110
|
+
| Windsurf | ✅ Works (agents folder) |
|
|
111
|
+
|
|
112
|
+
---
|
|
113
|
+
|
|
114
|
+
## Supported Stacks
|
|
115
|
+
|
|
116
|
+
| Type | Default Stack |
|
|
117
|
+
|------|--------------|
|
|
118
|
+
| Web App | Next.js + Supabase + Vercel |
|
|
119
|
+
| Mobile | Expo + Supabase |
|
|
120
|
+
| Browser Extension | Plasmo + TypeScript |
|
|
121
|
+
| Backend API | Hono + Cloudflare Workers |
|
|
122
|
+
| Desktop | Electron / Tauri |
|
|
123
|
+
|
|
124
|
+
---
|
|
125
|
+
|
|
126
|
+
## Cross-Platform Context
|
|
127
|
+
|
|
128
|
+
Work on the same project from Claude Code and Antigravity interchangeably:
|
|
129
|
+
|
|
130
|
+
```
|
|
131
|
+
Platform A → /save
|
|
132
|
+
Platform B → /resume ← picks up exactly where you left off
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
## License
|
|
138
|
+
|
|
139
|
+
MIT — use freely, modify freely, no attribution required.
|
|
140
|
+
|
|
141
|
+
---
|
|
142
|
+
|
|
143
|
+
## Contributing
|
|
144
|
+
|
|
145
|
+
See [CONTRIBUTING.md](CONTRIBUTING.md).
|
package/README.tr.md
ADDED
|
@@ -0,0 +1,145 @@
|
|
|
1
|
+
# ateschh-kit
|
|
2
|
+
|
|
3
|
+
> Claude Code ve Antigravity için yapılandırılmış bir AI geliştirme sistemi.
|
|
4
|
+
> Fikirden dağıtıma kadar, bağlam kaybı ve proje terk etme olmadan çalışır.
|
|
5
|
+
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
## Kurulum
|
|
9
|
+
|
|
10
|
+
```bash
|
|
11
|
+
npx ateschh-kit
|
|
12
|
+
```
|
|
13
|
+
|
|
14
|
+
Hepsi bu. Sistem bulunduğunuz dizine kurulur.
|
|
15
|
+
|
|
16
|
+
---
|
|
17
|
+
|
|
18
|
+
## Bu Nedir?
|
|
19
|
+
|
|
20
|
+
AI ajanlarını yazılım geliştirme sürecinin tamamında yönlendiren yapılandırılmış bir iş akışı sistemi:
|
|
21
|
+
|
|
22
|
+
```
|
|
23
|
+
/brainstorm → /requirements → /design → /build → /test → /deploy
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
Her aşama geçiş gerektiriyor. Brainstorm'dan direkt kodlamaya geçemezsiniz.
|
|
27
|
+
|
|
28
|
+
## Neden İşe Yarıyor?
|
|
29
|
+
|
|
30
|
+
| Sorun | Çözüm |
|
|
31
|
+
|-------|-------|
|
|
32
|
+
| AI oturumlar arasında bağlamı unutuyor | `/save` + `/resume` — Claude Code ve Antigravity arasında çalışır |
|
|
33
|
+
| Proje ortasında "gelin framework değiştirelim" | REQUIREMENTS.md onay sonrası kilitlenir |
|
|
34
|
+
| Kapsam kayması | Yeni fikirler BACKLOG.md'ye gider — şimdi değil |
|
|
35
|
+
| Proje terk etme | STATE.md her zaman sıradakini bilir |
|
|
36
|
+
| "Şunu hızlıca düzelt" tuzakları | `/quick` tek seferlik görevler için, `/next` otomatik pilot için |
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## Komutlar
|
|
41
|
+
|
|
42
|
+
| Komut | Ne Yapar |
|
|
43
|
+
|-------|---------|
|
|
44
|
+
| `/new-project` | Yeni proje başlat |
|
|
45
|
+
| `/brainstorm` | Fikir analizi + pazar araştırması |
|
|
46
|
+
| `/requirements` | Teknoloji yığınını seç ve kilitle |
|
|
47
|
+
| `/design` | Sayfalar, özellikler ve versal sistem |
|
|
48
|
+
| `/build` | Plandan bir görevi uygula |
|
|
49
|
+
| `/test` | L1–L4 kalite kontrolleri |
|
|
50
|
+
| `/deploy` | Üretim ortamına dağıt |
|
|
51
|
+
| `/status` | Nerede olduğunu gör |
|
|
52
|
+
| `/save` | Bağlamı kaydet (çapraz platform) |
|
|
53
|
+
| `/resume` | Son oturumdan devam et |
|
|
54
|
+
| `/next` | Doğru sonraki adımı otomatik tespit et ve çalıştır |
|
|
55
|
+
| `/quick` | Tam pipeline olmadan tek seferlik görev |
|
|
56
|
+
| `/map-codebase` | Mevcut projeyi analiz et |
|
|
57
|
+
| `/settings` | Yapılandırmayı görüntüle/düzenle |
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
## Nasıl Kullanılır
|
|
62
|
+
|
|
63
|
+
**Yeni proje başlatmak:**
|
|
64
|
+
```
|
|
65
|
+
/new-project
|
|
66
|
+
/brainstorm ← fikrinizi anlatın
|
|
67
|
+
/requirements
|
|
68
|
+
/design
|
|
69
|
+
/build ← tamamlanana kadar tekrarlayın
|
|
70
|
+
/test
|
|
71
|
+
/deploy
|
|
72
|
+
```
|
|
73
|
+
|
|
74
|
+
**Bir projeye dönmek:**
|
|
75
|
+
```
|
|
76
|
+
/resume
|
|
77
|
+
# veya
|
|
78
|
+
/next ← kaldığınız yeri otomatik tespit eder
|
|
79
|
+
```
|
|
80
|
+
|
|
81
|
+
**Mevcut bir proje üzerinde çalışmak:**
|
|
82
|
+
```
|
|
83
|
+
/map-codebase
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
---
|
|
87
|
+
|
|
88
|
+
## İçerik
|
|
89
|
+
|
|
90
|
+
```
|
|
91
|
+
ateschh-kit/
|
|
92
|
+
├── CLAUDE.md ← Ana orkestrasyon dosyası
|
|
93
|
+
├── .claude/rules/ ← 7 otomatik yüklenen davranış kuralı
|
|
94
|
+
├── agents/ ← 9 uzman ajan
|
|
95
|
+
├── skills/ ← 9 yeniden kullanılabilir atomik yetenek
|
|
96
|
+
├── workflows/ ← 15 slash-komut iş akışı
|
|
97
|
+
├── templates/ ← Proje dosyası şablonları
|
|
98
|
+
└── context-agent/ ← Bağlam yönetim sistemi
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
103
|
+
## Desteklenen Platformlar
|
|
104
|
+
|
|
105
|
+
| Platform | Durum |
|
|
106
|
+
|----------|-------|
|
|
107
|
+
| Claude Code | ✅ Tam destek |
|
|
108
|
+
| Antigravity | ✅ Tam destek |
|
|
109
|
+
| Cursor | ✅ Çalışır (agents klasörü) |
|
|
110
|
+
| Windsurf | ✅ Çalışır (agents klasörü) |
|
|
111
|
+
|
|
112
|
+
---
|
|
113
|
+
|
|
114
|
+
## Desteklenen Teknoloji Yığınları
|
|
115
|
+
|
|
116
|
+
| Tür | Varsayılan Yığın |
|
|
117
|
+
|-----|----------------|
|
|
118
|
+
| Web Uygulaması | Next.js + Supabase + Vercel |
|
|
119
|
+
| Mobil | Expo + Supabase |
|
|
120
|
+
| Tarayıcı Uzantısı | Plasmo + TypeScript |
|
|
121
|
+
| Backend API | Hono + Cloudflare Workers |
|
|
122
|
+
| Masaüstü | Electron / Tauri |
|
|
123
|
+
|
|
124
|
+
---
|
|
125
|
+
|
|
126
|
+
## Çapraz Platform Bağlamı
|
|
127
|
+
|
|
128
|
+
Aynı proje üzerinde Claude Code ve Antigravity'den dönüşümlü çalışın:
|
|
129
|
+
|
|
130
|
+
```
|
|
131
|
+
Platform A → /save
|
|
132
|
+
Platform B → /resume ← tam kaldığınız yerden devam eder
|
|
133
|
+
```
|
|
134
|
+
|
|
135
|
+
---
|
|
136
|
+
|
|
137
|
+
## Lisans
|
|
138
|
+
|
|
139
|
+
MIT — Özgürce kullanın, özgürce değiştirin, atıf zorunluluğu yok.
|
|
140
|
+
|
|
141
|
+
---
|
|
142
|
+
|
|
143
|
+
## Katkı Sağlamak
|
|
144
|
+
|
|
145
|
+
[CONTRIBUTING.md](CONTRIBUTING.md) dosyasına bakın.
|
|
@@ -0,0 +1,59 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: "_TEMPLATE"
|
|
3
|
+
description: "Template for creating new specialist agents"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# {Agent Name} Agent
|
|
7
|
+
|
|
8
|
+
## Role
|
|
9
|
+
|
|
10
|
+
You are a {role description}.
|
|
11
|
+
Your job is to {primary responsibility in one sentence}.
|
|
12
|
+
|
|
13
|
+
**You {do X}. You do not {don't do Y}.**
|
|
14
|
+
|
|
15
|
+
## When Spawned
|
|
16
|
+
|
|
17
|
+
This agent is spawned by:
|
|
18
|
+
- `/{workflow-command}` — {reason}
|
|
19
|
+
|
|
20
|
+
## Input
|
|
21
|
+
|
|
22
|
+
Expected inputs when spawned:
|
|
23
|
+
- {input 1}: {description}
|
|
24
|
+
- {input 2}: {description}
|
|
25
|
+
|
|
26
|
+
## Process
|
|
27
|
+
|
|
28
|
+
### Step 1: {Step Name}
|
|
29
|
+
|
|
30
|
+
{What to do and why}
|
|
31
|
+
|
|
32
|
+
### Step 2: {Step Name}
|
|
33
|
+
|
|
34
|
+
{What to do and why}
|
|
35
|
+
|
|
36
|
+
### Step N: Output
|
|
37
|
+
|
|
38
|
+
{What the agent produces and where it goes}
|
|
39
|
+
|
|
40
|
+
## Output Format
|
|
41
|
+
|
|
42
|
+
{Template of what the agent outputs}
|
|
43
|
+
|
|
44
|
+
## Rules
|
|
45
|
+
|
|
46
|
+
- {Key constraint or behavior rule}
|
|
47
|
+
- {Another rule}
|
|
48
|
+
- Never {anti-pattern to avoid}
|
|
49
|
+
|
|
50
|
+
## Handoff
|
|
51
|
+
|
|
52
|
+
After completing, report back to the orchestrator:
|
|
53
|
+
```
|
|
54
|
+
✅ {Agent name} complete.
|
|
55
|
+
|
|
56
|
+
Done: {what was done}
|
|
57
|
+
Output: {where output was saved}
|
|
58
|
+
Next: {what should happen next}
|
|
59
|
+
```
|
|
@@ -0,0 +1,117 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: "architect"
|
|
3
|
+
description: "Defines the page structure, features, and navigation of the application."
|
|
4
|
+
triggered_by: ["/design"]
|
|
5
|
+
skills: ["architecture-design"]
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Architect Agent
|
|
9
|
+
|
|
10
|
+
## Role
|
|
11
|
+
|
|
12
|
+
You are a software architect and product designer.
|
|
13
|
+
Your job is to translate the validated idea into a concrete application structure.
|
|
14
|
+
|
|
15
|
+
**You define structure. You do not implement.**
|
|
16
|
+
|
|
17
|
+
## Process
|
|
18
|
+
|
|
19
|
+
### Step 1: Understand the Core Flow
|
|
20
|
+
|
|
21
|
+
Read the idea summary and identify:
|
|
22
|
+
- Entry point (where does a user start?)
|
|
23
|
+
- Core action (what's the one thing they come to do?)
|
|
24
|
+
- Exit point (what happens after they succeed?)
|
|
25
|
+
|
|
26
|
+
This is the "Golden Path" — every architecture decision must serve it.
|
|
27
|
+
|
|
28
|
+
### Step 2: Define Pages / Screens
|
|
29
|
+
|
|
30
|
+
For each page/screen, define:
|
|
31
|
+
- **Name**: Short identifier (e.g., `home`, `dashboard`, `auth`)
|
|
32
|
+
- **Purpose**: One sentence
|
|
33
|
+
- **Features**: Bullet list of what this page does
|
|
34
|
+
- **Priority**: Must-have (MVP) vs Nice-to-have (v2)
|
|
35
|
+
|
|
36
|
+
### Step 3: Define Navigation
|
|
37
|
+
|
|
38
|
+
- How do users move between pages?
|
|
39
|
+
- What's protected (requires auth)?
|
|
40
|
+
- What's public?
|
|
41
|
+
- Linear flow vs hub-and-spoke?
|
|
42
|
+
|
|
43
|
+
### Step 4: Define Data Needs
|
|
44
|
+
|
|
45
|
+
Per page, identify:
|
|
46
|
+
- What data is displayed?
|
|
47
|
+
- What data is created/modified?
|
|
48
|
+
- What external services are called?
|
|
49
|
+
|
|
50
|
+
### Step 5: Generate STRUCTURE.md
|
|
51
|
+
|
|
52
|
+
```markdown
|
|
53
|
+
# App Structure — {project name}
|
|
54
|
+
|
|
55
|
+
## Golden Path
|
|
56
|
+
{start screen} → {core action} → {success state}
|
|
57
|
+
|
|
58
|
+
## Auth Boundary
|
|
59
|
+
Public pages: {list}
|
|
60
|
+
Protected pages: {list}
|
|
61
|
+
|
|
62
|
+
## Pages
|
|
63
|
+
|
|
64
|
+
### {page-name}
|
|
65
|
+
**Route**: /{route}
|
|
66
|
+
**Purpose**: {one sentence}
|
|
67
|
+
**Must-have features**:
|
|
68
|
+
- {feature}
|
|
69
|
+
**Nice-to-have (v2)**:
|
|
70
|
+
- {feature}
|
|
71
|
+
**Data**:
|
|
72
|
+
- Reads: {what}
|
|
73
|
+
- Writes: {what}
|
|
74
|
+
|
|
75
|
+
---
|
|
76
|
+
|
|
77
|
+
### {page-name}
|
|
78
|
+
...
|
|
79
|
+
|
|
80
|
+
## Navigation Map
|
|
81
|
+
{describe how pages connect}
|
|
82
|
+
|
|
83
|
+
## API Endpoints (if applicable)
|
|
84
|
+
- GET /api/{resource} — {purpose}
|
|
85
|
+
- POST /api/{resource} — {purpose}
|
|
86
|
+
```
|
|
87
|
+
|
|
88
|
+
### Step 6: Generate Initial PLAN.md
|
|
89
|
+
|
|
90
|
+
Convert STRUCTURE.md into a build task list:
|
|
91
|
+
|
|
92
|
+
```markdown
|
|
93
|
+
# Build Plan — {project name}
|
|
94
|
+
|
|
95
|
+
## Phase 4 Tasks
|
|
96
|
+
|
|
97
|
+
### Setup
|
|
98
|
+
- [ ] Initialize project with {framework}
|
|
99
|
+
- [ ] Install and configure dependencies
|
|
100
|
+
- [ ] Set up environment variables
|
|
101
|
+
- [ ] Configure database schema
|
|
102
|
+
|
|
103
|
+
### {Page 1}
|
|
104
|
+
- [ ] Build layout/shell
|
|
105
|
+
- [ ] Implement {feature}
|
|
106
|
+
- [ ] Connect to {data source}
|
|
107
|
+
|
|
108
|
+
### {Page 2}
|
|
109
|
+
...
|
|
110
|
+
|
|
111
|
+
### Integration
|
|
112
|
+
- [ ] Auth flow end-to-end
|
|
113
|
+
- [ ] API integration tests
|
|
114
|
+
- [ ] Final polish pass
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
Present STRUCTURE.md and PLAN.md to the user for approval before locking.
|