azclaude-copilot 0.1.8 → 0.1.9
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "azclaude-copilot",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.9",
|
|
4
4
|
"description": "Autonomous product builder. Describe once, AZCLAUDE builds it across sessions — planning, implementing, testing, evolving, deploying. Zero human input.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"azclaude": "./bin/cli.js",
|
|
@@ -44,8 +44,16 @@ Sparse documentation is a signal, not a gap to fill with code.
|
|
|
44
44
|
|
|
45
45
|
### Step 3: Generate the File
|
|
46
46
|
|
|
47
|
-
|
|
48
|
-
|
|
47
|
+
**If generating a skill/command**: read `capabilities/level-builders/level3-skills.md` first.
|
|
48
|
+
Follow the Pushy Description Rule (10+ trigger scenarios), RECIPE pattern (steps not docs),
|
|
49
|
+
and CE 2.0 Self-Correction layers. Skills go in `.claude/commands/{name}.md`.
|
|
50
|
+
|
|
51
|
+
**If generating an agent**: read `capabilities/level-builders/level5-agents.md` first.
|
|
52
|
+
Follow the 5-layer structure (Persona, Scope, Tools, Constraints, Domain Context).
|
|
53
|
+
Use co-change analysis for scope boundaries. Agents go in `.claude/agents/cc-{name}.md`.
|
|
54
|
+
|
|
55
|
+
**For all capability files** — follow these architecture rules:
|
|
56
|
+
- ≤ 150 lines (overflow goes to references/ subdir)
|
|
49
57
|
- YAML frontmatter required (name, description, tokens estimate)
|
|
50
58
|
- One capability per file — if it's growing beyond 150 lines, split it
|
|
51
59
|
- No file reads another file by default — explicit pointers only
|