azcodr 1.5.0 → 1.5.2

package/.agents/skills/agentic-architect/references/agents_md_template.md

@@ -1,62 +1,62 @@
-# Root & Nested AGENTS.md Template
-
-Use this template when bootstrapping or restructuring an `AGENTS.md` file according to the progressive disclosure architecture.
-
----
-
-```markdown
-# AGENTS.md
-
-> **[Workspace / Package Name] Directives**  
-> **Rule Zero:** Assume nothing. Every action must be grounded in verified evidence from this workspace or direct instructions from the user.
-
----
-
-## 1. Project Overview & Environment
-- **Purpose:** [1–2 sentences explaining what this project does and its core domain].
-- **Runtime & Tools:** [e.g. Node 24 / npm 11, package manager, key global scripts].
-- **High-Level Layout:**
-  - `apps/` — [High-level package boundaries].
-  - `packages/` — [Shared libraries/utilities].
-  - `docs/rules/` — [Modular progressive disclosure rules].
-
----
-
-## 2. Core Operating Framework
-- **Ground Truth Only:** A statement is only true if proven by a file, command output, or direct user instruction.
-- **Relentless Questioning Loop:** Before acting, answer:
-  1. What is current state?
-  2. What is exact goal?
-  3. What tools are available?
-  4. What could break?
-  5. How will we prove it works?
-- **Execution Stages:** `DISCOVER` ➔ `INTERROGATE` ➔ `PLAN` ➔ `EXECUTE` ➔ `VERIFY`.
-- **Action Boundaries:**
-  - **ALWAYS:** Read before editing; verify commands before running; verify results with evidence.
-  - **ASK FIRST:** Adding dependencies, deleting files, modifying DB schemas or existing tests.
-  - **NEVER:** Guess paths or flags; silently ignore errors; import external assumptions.
-
----
-
-## 3. Progressive Disclosure Rules
-
-Read these specialized rule files on demand when performing relevant tasks:
-
-| Domain | Rule Reference File | When to Consult |
-|---|---|---|
-| **Testing** | [docs/rules/test_driven_development.md](../../../../docs/rules/test_driven_development.md) | Writing acceptance/unit tests, coverage checks. |
-| **Multi-Tenancy** | [docs/rules/multitenancy_architecture.md](../../../../docs/rules/multitenancy_architecture.md) | Tenant context resolution, PostgreSQL RLS. |
-| **Database** | [docs/rules/database_design.md](../../../../docs/rules/database_design.md) | Relational integrity, ACID transactions, outbox pattern. |
-
----
-
-## 4. Harness Parity
-Keep `AGENTS.md`, `CLAUDE.md`, `agents.md`, `GEMINI.md`, `.cursorrules`, and `.windsurfrules` in sync via filesystem symlinks:
-```bash
-ln -sf AGENTS.md CLAUDE.md
-ln -sf AGENTS.md agents.md
-ln -sf AGENTS.md GEMINI.md
-ln -sf AGENTS.md .cursorrules
-ln -sf AGENTS.md .windsurfrules
-```
-```
+# Root & Nested AGENTS.md Template
+
+Use this template when bootstrapping or restructuring an `AGENTS.md` file according to the progressive disclosure architecture.
+
+---
+
+```markdown
+# AGENTS.md
+
+> **[Workspace / Package Name] Directives**  
+> **Rule Zero:** Assume nothing. Every action must be grounded in verified evidence from this workspace or direct instructions from the user.
+
+---
+
+## 1. Project Overview & Environment
+- **Purpose:** [1–2 sentences explaining what this project does and its core domain].
+- **Runtime & Tools:** [e.g. Node 24 / npm 11, package manager, key global scripts].
+- **High-Level Layout:**
+  - `apps/` — [High-level package boundaries].
+  - `packages/` — [Shared libraries/utilities].
+  - `docs/rules/` — [Modular progressive disclosure rules].
+
+---
+
+## 2. Core Operating Framework
+- **Ground Truth Only:** A statement is only true if proven by a file, command output, or direct user instruction.
+- **Relentless Questioning Loop:** Before acting, answer:
+  1. What is current state?
+  2. What is exact goal?
+  3. What tools are available?
+  4. What could break?
+  5. How will we prove it works?
+- **Execution Stages:** `DISCOVER` ➔ `INTERROGATE` ➔ `PLAN` ➔ `EXECUTE` ➔ `VERIFY`.
+- **Action Boundaries:**
+  - **ALWAYS:** Read before editing; verify commands before running; verify results with evidence.
+  - **ASK FIRST:** Adding dependencies, deleting files, modifying DB schemas or existing tests.
+  - **NEVER:** Guess paths or flags; silently ignore errors; import external assumptions.
+
+---
+
+## 3. Progressive Disclosure Rules
+
+Read these specialized rule files on demand when performing relevant tasks:
+
+| Domain | Rule Reference File | When to Consult |
+|---|---|---|
+| **Testing** | [docs/rules/test_driven_development.md](../../../../docs/rules/test_driven_development.md) | Writing acceptance/unit tests, coverage checks. |
+| **Multi-Tenancy** | [docs/rules/multitenancy_architecture.md](../../../../docs/rules/multitenancy_architecture.md) | Tenant context resolution, PostgreSQL RLS. |
+| **Database** | [docs/rules/database_design.md](../../../../docs/rules/database_design.md) | Relational integrity, ACID transactions, outbox pattern. |
+
+---
+
+## 4. Harness Parity
+Keep `AGENTS.md`, `CLAUDE.md`, `agents.md`, `GEMINI.md`, `.cursorrules`, and `.windsurfrules` in sync via filesystem symlinks:
+```bash
+ln -sf AGENTS.md CLAUDE.md
+ln -sf AGENTS.md agents.md
+ln -sf AGENTS.md GEMINI.md
+ln -sf AGENTS.md .cursorrules
+ln -sf AGENTS.md .windsurfrules
+```
+```

package/.agents/skills/agentic-architect/references/refinement_workflow.md

@@ -1,32 +1,32 @@
-# Continuous Skill & Rule Refinement Workflow
-
-> **Purpose:** Iteratively improve AI code output by harvesting manual developer edits and converting recurring mistakes into explicit skill rules.
-
----
-
-## The 4-Step Refinement Loop
-
-```
-1. AI Draft Generated ──► 2. Human Manual Edit ──► 3. Extract Gaps & Anti-Patterns ──► 4. Update Skill
-```
-
-### 1. Capture Raw Output
-When prompting the AI to execute a complex task (e.g. drafting an article, building a complex form, scaffolding an endpoint), retain the raw generated output before making edits.
-
-### 2. Perform Gold-Standard Edits
-Manually modify the generated file to match production quality:
-- Adjust architectural choices.
-- Fix styling, accessibility, or type annotations.
-- Correct API response shapes or error handling.
-
-### 3. Analyze the Diff
-Compare the initial AI draft against the final human version:
-- What did the AI assume that was incorrect?
-- What repetitive boilerplate did the AI miss?
-- What unnecessary packages, methods, or complex patterns did it introduce?
-
-### 4. Feed Back into the Skill
-Update the relevant skill or rule file:
-- Add positive examples under the workflow section.
-- **Crucial:** Add explicit negative rules in the **"Gotchas & What NOT to Do"** section (e.g. *"DO NOT use window.confirm; use @radix-ui/react-alert-dialog"*).
-- If a step failed due to non-deterministic CLI flags, write an executable helper script under `scripts/`.
+# Continuous Skill & Rule Refinement Workflow
+
+> **Purpose:** Iteratively improve AI code output by harvesting manual developer edits and converting recurring mistakes into explicit skill rules.
+
+---
+
+## The 4-Step Refinement Loop
+
+```
+1. AI Draft Generated ──► 2. Human Manual Edit ──► 3. Extract Gaps & Anti-Patterns ──► 4. Update Skill
+```
+
+### 1. Capture Raw Output
+When prompting the AI to execute a complex task (e.g. drafting an article, building a complex form, scaffolding an endpoint), retain the raw generated output before making edits.
+
+### 2. Perform Gold-Standard Edits
+Manually modify the generated file to match production quality:
+- Adjust architectural choices.
+- Fix styling, accessibility, or type annotations.
+- Correct API response shapes or error handling.
+
+### 3. Analyze the Diff
+Compare the initial AI draft against the final human version:
+- What did the AI assume that was incorrect?
+- What repetitive boilerplate did the AI miss?
+- What unnecessary packages, methods, or complex patterns did it introduce?
+
+### 4. Feed Back into the Skill
+Update the relevant skill or rule file:
+- Add positive examples under the workflow section.
+- **Crucial:** Add explicit negative rules in the **"Gotchas & What NOT to Do"** section (e.g. *"DO NOT use window.confirm; use @radix-ui/react-alert-dialog"*).
+- If a step failed due to non-deterministic CLI flags, write an executable helper script under `scripts/`.

package/.agents/skills/agentic-architect/references/skill_architecture_inquiry.md

@@ -1,63 +1,63 @@
-# Relentless Skill Architecture Inquiry Guide
-
-> **Core Rule:** Never assume what a skill needs. Relentlessly interrogate all 7 branches before authoring or modifying any `SKILL.md`.
-
----
-
-## The 7 Core Inquiry Branches
-
-```
-[Skill Request / Idea]
-       │
-       ▼
-[Branch 1: Placement & Scope]
-       ├─ All prompts repository-wide? ─────────► Root AGENTS.md
-       ├─ One monorepo package only? ──────────► Nested package AGENTS.md
-       ├─ Continuous domain coding rule? ──────► docs/rules/*.md
-       └─ Specialized on-demand workflow? ─────► .agents/skills/<name>/
-       │
-       ▼
-[Branch 2: Trigger Intent & Anti-Triggers]
-       ├─ What explicit user request triggers this?
-       ├─ Imperative phrasing: 'Use when the user wants to...' (< 1024 chars)
-       └─ Negative boundaries: 'Do NOT use for...'
-       │
-       ▼
-[Branch 3: Domain Ground Truth (Purge Fluff)]
-       ├─ What does the LLM already know from pre-training? (PURGE)
-       └─ What is strictly proprietary/unique to this repository? (KEEP)
-       │
-       ▼
-[Branch 4: Anti-Patterns & Gotchas (What NOT to Do)]
-       ├─ What mistakes has the AI actually made in past attempts?
-       └─ Formulate 3–5 explicit negative constraints ('DO NOT...')
-       │
-       ▼
-[Branch 5: Determinism vs. Stochastic LLM]
-       ├─ Are there brittle command lines or JSON formatting steps?
-       └─ Should these be deterministic helper scripts in scripts/?
-       │
-       ▼
-[Branch 6: Progressive Disclosure (< 500 Lines)]
-       ├─ Is SKILL.md under 500 lines?
-       ├─ Are deep manuals offloaded to references/?
-       └─ Are static schemas or templates offloaded to resources/?
-       │
-       ▼
-[Branch 7: Verification & Feedback Loop]
-       ├─ What structured output format proves success?
-       ├─ What self-validation checklist must be satisfied?
-       └─ How will diffs between AI drafts and human edits be harvested?
-```
-
----
-
-## Inquiry Interview Template
-
-When asking the user or interrogating the workspace, use this questionnaire:
-
-1. **Scope:** Is this workflow continuous (applies whenever writing code in this domain) or episodic (triggered only on explicit request)?
-2. **Triggers:** When should the AI automatically reach for this skill? What tasks should it actively *refuse* to use this skill for?
-3. **Pitfalls:** What has the AI historically messed up when doing this task (e.g. hallucinating dependencies, using wrong flags, creating leaky abstractions)?
-4. **Determinism:** Are there shell commands or formatting rules that should be guaranteed with a script rather than left to LLM chance?
-5. **Output Standard:** What does the ideal, gold-standard output look like?
+# Relentless Skill Architecture Inquiry Guide
+
+> **Core Rule:** Never assume what a skill needs. Relentlessly interrogate all 7 branches before authoring or modifying any `SKILL.md`.
+
+---
+
+## The 7 Core Inquiry Branches
+
+```
+[Skill Request / Idea]
+       │
+       ▼
+[Branch 1: Placement & Scope]
+       ├─ All prompts repository-wide? ─────────► Root AGENTS.md
+       ├─ One monorepo package only? ──────────► Nested package AGENTS.md
+       ├─ Continuous domain coding rule? ──────► docs/rules/*.md
+       └─ Specialized on-demand workflow? ─────► .agents/skills/<name>/
+       │
+       ▼
+[Branch 2: Trigger Intent & Anti-Triggers]
+       ├─ What explicit user request triggers this?
+       ├─ Imperative phrasing: 'Use when the user wants to...' (< 1024 chars)
+       └─ Negative boundaries: 'Do NOT use for...'
+       │
+       ▼
+[Branch 3: Domain Ground Truth (Purge Fluff)]
+       ├─ What does the LLM already know from pre-training? (PURGE)
+       └─ What is strictly proprietary/unique to this repository? (KEEP)
+       │
+       ▼
+[Branch 4: Anti-Patterns & Gotchas (What NOT to Do)]
+       ├─ What mistakes has the AI actually made in past attempts?
+       └─ Formulate 3–5 explicit negative constraints ('DO NOT...')
+       │
+       ▼
+[Branch 5: Determinism vs. Stochastic LLM]
+       ├─ Are there brittle command lines or JSON formatting steps?
+       └─ Should these be deterministic helper scripts in scripts/?
+       │
+       ▼
+[Branch 6: Progressive Disclosure (< 500 Lines)]
+       ├─ Is SKILL.md under 500 lines?
+       ├─ Are deep manuals offloaded to references/?
+       └─ Are static schemas or templates offloaded to resources/?
+       │
+       ▼
+[Branch 7: Verification & Feedback Loop]
+       ├─ What structured output format proves success?
+       ├─ What self-validation checklist must be satisfied?
+       └─ How will diffs between AI drafts and human edits be harvested?
+```
+
+---
+
+## Inquiry Interview Template
+
+When asking the user or interrogating the workspace, use this questionnaire:
+
+1. **Scope:** Is this workflow continuous (applies whenever writing code in this domain) or episodic (triggered only on explicit request)?
+2. **Triggers:** When should the AI automatically reach for this skill? What tasks should it actively *refuse* to use this skill for?
+3. **Pitfalls:** What has the AI historically messed up when doing this task (e.g. hallucinating dependencies, using wrong flags, creating leaky abstractions)?
+4. **Determinism:** Are there shell commands or formatting rules that should be guaranteed with a script rather than left to LLM chance?
+5. **Output Standard:** What does the ideal, gold-standard output look like?

package/.agents/skills/agentic-architect/references/skill_template.md

@@ -1,56 +1,56 @@
-# Progressive Disclosure Skill Template
-
-Use this template when creating new skills under `.agents/skills/<skill-name>/SKILL.md`.
-
----
-
-```markdown
----
-name: <skill-name>
-description: Use when [clear trigger conditions, e.g. implementing authentication, generating emails, running migrations]. Do not use for [explicit boundaries, e.g. general bug fixes or frontend styling].
----
-
-# [Skill Title]
-
-> **Purpose:** [Brief 1–2 sentence summary of what this skill achieves].
-
----
-
-## 1. Trigger Conditions
-- When the user explicitly requests: `[Examples]`
-- When performing tasks involving: `[File patterns or domains]`
-- **Do NOT trigger when:** `[Negative conditions]`
-
----
-
-## 2. Core Workflow Steps
-1. **[Step 1: Discover & Validate]**: Inspect current state before modifying code.
-2. **[Step 2: Execute Core Logic]**: Follow established patterns.
-3. **[Step 3: Self-Check & Verify]**: Run test commands or validation scripts.
-
----
-
-## 3. Gotchas & What NOT to Do
-- **DO NOT** [Specific common AI mistake #1].
-- **DO NOT** [Specific common AI mistake #2].
-- **DO NOT** [Specific common AI mistake #3].
-
----
-
-## 4. Structured Output Template
-Provide consistent formatting for results:
-```markdown
-### Summary of Changes
-- **Action**: ...
-- **Files Affected**: ...
-- **Verification Evidence**: ...
-```
-
----
-
-## 5. Subdirectories & Progressive Resources
-- Deep reference documentation: `references/`
-- Deterministic helper scripts: `scripts/`
-- Static schemas, templates, or mock data: `resources/`
-- Reference implementations and patterns: `examples/`
-```
+# Progressive Disclosure Skill Template
+
+Use this template when creating new skills under `.agents/skills/<skill-name>/SKILL.md`.
+
+---
+
+```markdown
+---
+name: <skill-name>
+description: Use when [clear trigger conditions, e.g. implementing authentication, generating emails, running migrations]. Do not use for [explicit boundaries, e.g. general bug fixes or frontend styling].
+---
+
+# [Skill Title]
+
+> **Purpose:** [Brief 1–2 sentence summary of what this skill achieves].
+
+---
+
+## 1. Trigger Conditions
+- When the user explicitly requests: `[Examples]`
+- When performing tasks involving: `[File patterns or domains]`
+- **Do NOT trigger when:** `[Negative conditions]`
+
+---
+
+## 2. Core Workflow Steps
+1. **[Step 1: Discover & Validate]**: Inspect current state before modifying code.
+2. **[Step 2: Execute Core Logic]**: Follow established patterns.
+3. **[Step 3: Self-Check & Verify]**: Run test commands or validation scripts.
+
+---
+
+## 3. Gotchas & What NOT to Do
+- **DO NOT** [Specific common AI mistake #1].
+- **DO NOT** [Specific common AI mistake #2].
+- **DO NOT** [Specific common AI mistake #3].
+
+---
+
+## 4. Structured Output Template
+Provide consistent formatting for results:
+```markdown
+### Summary of Changes
+- **Action**: ...
+- **Files Affected**: ...
+- **Verification Evidence**: ...
+```
+
+---
+
+## 5. Subdirectories & Progressive Resources
+- Deep reference documentation: `references/`
+- Deterministic helper scripts: `scripts/`
+- Static schemas, templates, or mock data: `resources/`
+- Reference implementations and patterns: `examples/`
+```