contextos-agents 2.0.0 → 2.1.1

package/.agents/compiled/registry.v2.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 2,
   "compilerVersion": "2.0.0",
-  "sourceGraphHash": "sha256:c15f3691d9ed833630152b65959fdef465d88a7cf5bb27d44a086621e20c89c1",
+  "sourceGraphHash": "sha256:938c5051454535087e03f26af35c434cf194f414d2ec8044b4ae754e8524cf37",
   "skills": {
     "context-manager": {
       "id": "context-manager",
@@ -66,9 +66,9 @@
       "category": "general",
       "type": "compiler",
       "entrypoint": "SKILL.md",
-      "entrypointHash": "sha256:f28a8b6df5cf6d0dc8b32d8e4149f866b59ee11da0c1c050f766a0009674ca86",
-      "resourceTreeHash": "sha256:697cd51226283b147f719e2f4074acb058be1f3fe42714a3babb771e52e26a73",
-      "estimatedTokens": 1227,
+      "entrypointHash": "sha256:ab14bcd603573c975a69cb95b5ef8a305de8eb888c81c20c994121313f017239",
+      "resourceTreeHash": "sha256:48568f01d27fa53e2e01a6a63afd60eb2d43cabdc9eb2cfe6f02a2b67d0f53e1",
+      "estimatedTokens": 1365,
       "source": ".agents/core/skills/context-os/skill.yaml",
       "signals": {
         "aliases": [
@@ -85,7 +85,7 @@
       },
       "context": {
         "priority": 50,
-        "estimatedTokens": 1227
+        "estimatedTokens": 1365
       },
       "resources": [
         {
@@ -137,9 +137,9 @@
       "category": "general",
       "type": "instruction-only",
       "entrypoint": "SKILL.md",
-      "entrypointHash": "sha256:0985a21360cdd796a2f2970b659b6a7a1cdd55672dd35b0292400f9a0092b556",
-      "resourceTreeHash": "sha256:6e2e654c903e1043609c1f7f36980a19c1e20e35bc3fa337ad051293f1e9124c",
-      "estimatedTokens": 3065,
+      "entrypointHash": "sha256:88b606d086f63c5e293630ad84ff524d2542f2953fc1a5a451bd77352073b0ad",
+      "resourceTreeHash": "sha256:e78a054d8f54a72550cf10d551a82f56015aedb3f16a14021e654574bad5804f",
+      "estimatedTokens": 3083,
       "source": ".agents/core/skills/engineering-workflow/skill.yaml",
       "signals": {
         "aliases": [
@@ -156,7 +156,7 @@
       },
       "context": {
         "priority": 50,
-        "estimatedTokens": 3065
+        "estimatedTokens": 3083
       },
       "resources": [
         {
@@ -188,9 +188,9 @@
       "category": "general",
       "type": "instruction-only",
       "entrypoint": "SKILL.md",
-      "entrypointHash": "sha256:677c7229e8b483990cf4b441b990328f5933127a7c449830fe2786cd232321c4",
-      "resourceTreeHash": "sha256:38e0e3e512df2855647a083a6e0ae759a3af613b7f2e2848046b8d6998143539",
-      "estimatedTokens": 1868,
+      "entrypointHash": "sha256:bd091c13a5c15c2ac55a8c27b309ffdd8e0a5a8b8260198808b70e45e685b9fd",
+      "resourceTreeHash": "sha256:8ae82b8dd89128820c8b28c7e9e8aac878f363381dd2a11043b8aff9d03ae35e",
+      "estimatedTokens": 1890,
       "source": ".agents/core/skills/gemini-precision/skill.yaml",
       "signals": {
         "aliases": [
@@ -207,13 +207,21 @@
       },
       "context": {
         "priority": 50,
-        "estimatedTokens": 1868
+        "estimatedTokens": 1890
       },
       "resources": [
+        {
+          "path": "EXAMPLES.md",
+          "mode": "on-demand"
+        },
         {
           "path": "SKILL.md",
           "mode": "on-demand"
         },
+        {
+          "path": "TROUBLESHOOTING.md",
+          "mode": "on-demand"
+        },
         {
           "path": "VALIDATION.json",
           "mode": "on-demand"
@@ -231,9 +239,9 @@
       "category": "general",
       "type": "instruction-only",
       "entrypoint": "SKILL.md",
-      "entrypointHash": "sha256:faaa89d02bf41416c173e6387e5c9c5065cfe4d82e76c2ae244b77c6cecd3230",
-      "resourceTreeHash": "sha256:f83fba0726700070887643c7e20a0584ba29b0f96c2587bcd834860362ce7a95",
-      "estimatedTokens": 1774,
+      "entrypointHash": "sha256:09334359de594f9c3e667ae0660db9a5c977c583b25ccf7de71fe25b7134454e",
+      "resourceTreeHash": "sha256:0bcfb511ef61a6782e3394c0779e5f5eed1833aff6e24c7749957df209c6185a",
+      "estimatedTokens": 1791,
       "source": ".agents/core/skills/gstack-roles/skill.yaml",
       "signals": {
         "aliases": [
@@ -250,7 +258,7 @@
       },
       "context": {
         "priority": 50,
-        "estimatedTokens": 1774
+        "estimatedTokens": 1791
       },
       "resources": [
         {
@@ -333,9 +341,9 @@
       "category": "backend",
       "type": "instruction-only",
       "entrypoint": "SKILL.md",
-      "entrypointHash": "sha256:151bc9080230cdec8e1de9d703d03b739ab0767e24fb2551acd5cf58feb4f3ab",
-      "resourceTreeHash": "sha256:da5be685a6db8c48faeb74722891816960e4b6a86378b680f045a81a204ac572",
-      "estimatedTokens": 1615,
+      "entrypointHash": "sha256:5daec60e9bb1c49a2b66e43d73e897397507e3604ef4bf02588d35cfd59b1903",
+      "resourceTreeHash": "sha256:b4302851046e1faffc18bc600c79d92d1da7f31bed03781eee89e84ddedc4956",
+      "estimatedTokens": 2237,
       "source": ".agents/core/skills/security/skill.yaml",
       "signals": {
         "aliases": [
@@ -403,7 +411,7 @@
       },
       "context": {
         "priority": 90,
-        "estimatedTokens": 1615
+        "estimatedTokens": 2237
       },
       "resources": [
         {
@@ -421,10 +429,6 @@
         {
           "path": "VALIDATION.json",
           "mode": "on-demand"
-        },
-        {
-          "path": "security.md",
-          "mode": "on-demand"
         }
       ],
       "deprecated": false,

package/.agents/compiled/registry.v2.sha256

@@ -1 +1 @@
-sha256:c15f3691d9ed833630152b65959fdef465d88a7cf5bb27d44a086621e20c89c1  registry.v2.json
+sha256:938c5051454535087e03f26af35c434cf194f414d2ec8044b4ae754e8524cf37  registry.v2.json

package/.agents/core/skills/context-os/SKILL.md

@@ -8,11 +8,11 @@ description: >-
 
 ## Overview
 
-Deterministic context compiler and policy engine for AI coding agents. Standardizes software engineering workflows across requirements, architecture, atomic task planning, implementation, verification, and release.
+Deterministic context compiler and policy engine for AI coding agents. Governs repository policy configuration, skill dependency graphs, profile management, and multi-agent configuration export.
 
 ## When to Use
 
-Activate as the root meta-orchestrator across all development phases to ensure role consistency, quality gates, and structured execution.
+Activate when managing project configuration, resolving skill dependencies, compiling rules for editors, or defining repository-level agent standards. (For task-specific file and context budgeting, use `context-manager`).
 
 ## Rules & Patterns
 
@@ -46,10 +46,10 @@ intent:
 For each required layer, load the skill graph:
 
 1. Read `skill.yaml` from each relevant skill directory
-2. Resolve `requires` — load mandatory dependencies
-3. Check `conflicts` — ensure no incompatible skills are loaded
-4. Apply `optional` — suggest but don't force
-5. Respect project profile (if set) — apply rules from `profiles/`
+2. Resolve `requires` - load mandatory dependencies
+3. Check `conflicts` - ensure no incompatible skills are loaded
+4. Apply `optional` - suggest but don't force
+5. Respect project profile (if set) - apply rules from `profiles/`
 
 **Dependency resolution example:**
 
@@ -67,48 +67,45 @@ Suggested: [tailwind, prisma, next-auth]
 
 Assemble context from three levels:
 
-**Level 1 — Vision (always available):**
+**Level 1 - Vision (always available):**
 
-- `docs/PRD.md` — what are we building
-- `docs/ROADMAP.md` — where are we going
-- `docs/PROJECT_GRAPH.md` — project structure
+- `docs/PRD.md` - what are we building
+- `docs/ROADMAP.md` - where are we going
+- `docs/PROJECT_GRAPH.md` - project structure
+- `docs/API.md` - API specification (optional, when backend API layer is present)
+- `docs/UI.md` - UI/UX specification (optional, when UI layer is present)
 
-**Level 2 — Architecture (load when needed):**
+**Level 2 - Architecture (load when needed):**
 
-- `docs/ARCHITECTURE.md` — system design
-- `docs/DATABASE.md` — data model
-- `docs/API.md` — API contracts
-- `docs/decisions/` — prior decisions
+- `docs/ARCHITECTURE.md` - system design and boundaries
+- `docs/decisions/` - architecture decision records (ADRs)
+- `docs/PRODUCT_BOUNDARIES.md` - maturity boundaries and non-promises
+- `references/context-rules.md` - dynamic context selection and compilation rules
 
-**Level 3 — Development (load per task):**
+**Level 3 - Task-Specific Context (load per task):**
 
-- Relevant skill `.md` files
-- `docs/UI.md` — for frontend tasks
-- `docs/TASKS.md` — current sprint
+- Relevant skill documents from `.agents/skills/`
+- Target code and test files within planned blast radius
 
-**Context Filtering Rules:**
-See `references/context-rules.md` for the full mapping of task types to required documents.
+### Stage 4: Focused Context Selection
 
-### Stage 4: Prompt Optimization
+Before sending context to the AI coding assistant:
 
-Before sending to the AI agent:
+1. Select only skills relevant to the task domain and touched files
+2. Prioritize: task goal > architectural constraints > project conventions
+3. Include active Decision Records that affect the target component
+4. Enforce quality guardrails and verification criteria
 
-1. Remove sections not relevant to the current task
-2. Prioritize: current task context > architecture > vision
-3. Include recent Decision Records that affect the current task
-4. Add coding rules from the loaded skills
-
-## Commands
+## Core CLI Commands
 
 | Command | Action |
 | --- | --- |
-| `ctx init` | Analyze project idea, generate all docs |
-| `ctx plan` | Generate development plan from PRD |
-| `ctx compile` | Compile context for a specific task |
-| `ctx update` | Update changed documents |
-| `ctx graph` | Show/update Project Graph |
-| `ctx doctor` | Validate skill dependencies, check for conflicts |
-| `ctx explain` | Explain why specific context was loaded |
+| `contextos init` | Initialize `.agents/` folder and bootstrap profiles |
+| `contextos export <agent>` | Compile skills for target agent (`gemini`, `claude`, `cursor`, `copilot`, `aider`, `zed`, `all`) |
+| `contextos resolve "<task>"` | Dynamically resolve relevant skills, rules, and risk level for task |
+| `contextos validate` | Validate skill schemas, dependencies, and detect configuration drift |
+| `contextos doctor` | Pre-flight diagnostics for skills, profiles, and compiler synchronization |
+| `contextos watch` | Background file watcher for continuous auto-compilation |
 
 ## Project Initialization Flow
 
@@ -126,7 +123,7 @@ When user says something like "Сделай CRM для стоматологии"
 3. **Select profile** (startup/enterprise/mvp/hackathon)
 4. **Resolve skills** (Stage 2)
 5. **Generate all documents** using `generators/` skill
-6. **Create Project Graph** — the master map of modules → features → tasks → files → skills
+6. **Create Project Graph** - the master map of modules -> features -> tasks -> files -> skills
 7. **Output agent config** using `adapters/` skill
 
 ## Skill Discovery

package/.agents/core/skills/engineering-workflow/SKILL.md

@@ -45,7 +45,7 @@ Inspired by [addyosmani/agent-skills](https://github.com/addyosmani/agent-skills
 
 ---
 
-### Phase 1: DEFINE — /spec
+### Phase 1: DEFINE - /spec
 
 **Auto-activates → `[ROLE: Product Manager]`**
 
@@ -79,8 +79,8 @@ Before writing the spec, if there is ambiguity, high blast radius, or multiple a
 ### Technical Approach
 [Read the relevant code. Understand what changes where.]
 Files affected:
-- `src/X.js` — [what changes]
-- `src/Y.js` — [what changes]
+- `src/X.js` - [what changes]
+- `src/Y.js` - [what changes]
 
 ### Acceptance Criteria
 - [ ] Given [context], when [action], then [result]
@@ -93,7 +93,7 @@ Files affected:
 
 ---
 
-### Phase 2: PLAN — /plan
+### Phase 2: PLAN - /plan
 
 **Auto-activates → `[ROLE: Architect]`**
 
@@ -111,7 +111,7 @@ Organize tasks as **Thin Vertical Slices** rather than horizontal layers:
 - Each task must be **completable in < 2 hours** of focused work.
 - Each task must be **independently testable**.
 - Tasks must be **ordered by dependency** (blocking tasks first).
-- Each task gets a **test requirement** — no task without a test.
+- Each task gets a **test requirement** - no task without a test.
 
 #### Plan Template
 
@@ -136,13 +136,13 @@ Organize tasks as **Thin Vertical Slices** rather than horizontal layers:
 - [Risk 1]: [Mitigation]
 - [Risk 2]: [Mitigation]
 
-### STOP — Awaiting Approval
+### STOP - Awaiting Approval
 Do not proceed to BUILD until this plan is approved.
 ```
 
 ---
 
-### Phase 3: BUILD — /build
+### Phase 3: BUILD - /build
 
 **Auto-activates → `[ROLE: Senior Developer]`**
 
@@ -150,12 +150,12 @@ Implement one task at a time. Commit after each task.
 
 #### Build Rules
 
-1. **One task per commit** — atomic, descriptive commit messages.
-2. **Write the test FIRST** (TDD — red-green-refactor).
-3. **No dead code** — if it's not tested, it's not shipped.
-4. **No TODOs in committed code** — resolve or create a tracked issue.
-5. **Read before writing** — understand the surrounding code before changing it.
-6. **Limit the blast radius** — modify ONLY the files explicitly listed in the current task's plan. Do NOT rewrite adjacent components, hooks, or utilities unless strictly required AND approved.
+1. **One task per commit** - atomic, descriptive commit messages.
+2. **Write the test FIRST** (TDD - red-green-refactor).
+3. **No dead code** - if it's not tested, it's not shipped.
+4. **No TODOs in committed code** - resolve or create a tracked issue.
+5. **Read before writing** - understand the surrounding code before changing it.
+6. **Limit the blast radius** - modify ONLY the files explicitly listed in the current task's plan. Do NOT rewrite adjacent components, hooks, or utilities unless strictly required AND approved.
 
 #### Commit Message Format
 
@@ -172,7 +172,7 @@ Types: `feat`, `fix`, `refactor`, `test`, `docs`, `chore`
 
 ---
 
-### Phase 4: VERIFY — /test
+### Phase 4: VERIFY - /test
 
 **Auto-activates → `[ROLE: QA Lead]`**
 
@@ -193,7 +193,7 @@ Tests are proof, not an afterthought.
 
 For complex React components, prioritize testing _user behavior_ over internal state:
 
-- Use **React Testing Library** (`userEvent`, `screen.getByRole`) — test what the user sees.
+- Use **React Testing Library** (`userEvent`, `screen.getByRole`) - test what the user sees.
 - Use **Playwright** for critical user flows (login, checkout, form submit).
 - Do NOT test implementation details (internal state, private methods, component structure).
 - Focus on: "When user clicks X, does Y appear?" not "Does `useState` hold the right value?"
@@ -220,7 +220,7 @@ Before moving to Review, verify:
 
 ---
 
-### Phase 5: REVIEW — /review
+### Phase 5: REVIEW - /review
 
 **Auto-activates → `[ROLE: Staff Engineer]` + `[ROLE: Senior Designer]` for UI tasks**
 
@@ -240,7 +240,7 @@ Inspired by [obra/superpowers](https://github.com/obra/superpowers):
 
 ---
 
-### Phase 5.5: SIMPLIFY — /simplify
+### Phase 5.5: SIMPLIFY - /simplify
 
 **Auto-activates → `[ROLE: Staff Engineer]` (Ponytail Mindset)**
 
@@ -253,7 +253,7 @@ Before merging, ruthlessly simplify:
 
 ---
 
-### Phase 6: SHIP — /ship
+### Phase 6: SHIP - /ship
 
 **Auto-activates → `[ROLE: Release Engineer]`**
 
@@ -267,8 +267,7 @@ Only ship when all gates are green.
 - [ ] Docs updated (README, API docs, changelogs)
 - [ ] Breaking changes documented
 - [ ] Rollback plan exists
-- [ ] Vercel Preview Deployment is successful and manually verified
-- [ ] Core Web Vitals pass in preview (LCP < 2.5s, CLS < 0.1, INP < 200ms)
+- [ ] Preview / staging deployment verified (if applicable, e.g. Vercel Preview and Core Web Vitals for frontend deployments)
 
 #### Operational Self-Improvement
 
@@ -311,6 +310,7 @@ export async function POST(req) {
 - [ ] Implementation plan broken down into vertical tasks < 2 hours each.
 - [ ] Tests written before implementation (TDD/BDD).
 - [ ] Code reviewed against correctness, security, performance, and design gates.
+- [ ] Staged security and quality check passes (`contextos scan --staged --enforce`).
 - [ ] Simplification ladder executed before shipping.
 
 ---
@@ -337,7 +337,7 @@ export async function POST(req) {
 
 When completing a task or workflow, you must explicitly report your final status as the last part of your output:
 
-- **DONE** — completed with evidence.
-- **DONE_WITH_CONCERNS** — completed, but list concerns.
-- **BLOCKED** — cannot proceed; state blocker and what was tried.
-- **NEEDS_CONTEXT** — missing info; state exactly what is needed.
+- **DONE** - completed with evidence.
+- **DONE_WITH_CONCERNS** - completed, but list concerns.
+- **BLOCKED** - cannot proceed; state blocker and what was tried.
+- **NEEDS_CONTEXT** - missing info; state exactly what is needed.

package/.agents/core/skills/gemini-precision/EXAMPLES.md

@@ -0,0 +1,72 @@
+# gemini-precision Examples - Anti-patterns vs ContextOS Standard
+
+## Example 1: Read-Before-Write Invariant (Zero Assumptions)
+
+### Anti-pattern: Hallucinated Import and Signature
+
+```typescript
+// BAD: Assuming the module exists and export is a default function
+import hashPassword from 'src/utils/crypto';
+const hash = hashPassword(password);
+```
+
+### Best practice: ContextOS Standard (Inspected Active Codebase First)
+
+```typescript
+// GOOD: Inspected src/lib/auth.ts via view_file before writing code
+import { hashSecret, ARGON2_CONFIG } from '../lib/auth.js';
+const hash = await hashSecret(password, ARGON2_CONFIG);
+```
+
+---
+
+## Example 2: Zero-Placeholder Invariant (Complete Code Only)
+
+### Anti-pattern: Lazy Stubs and Ellipsis Comments
+
+```typescript
+// BAD: Emitting incomplete code with TODOs and ellipsis
+export function processTransaction(tx: Transaction) {
+  // TODO: validate transaction balance
+  // ... rest of implementation stays here ...
+  return { status: 'ok' };
+}
+```
+
+### Best practice: ContextOS Standard (100% Drop-in Compilable)
+
+```typescript
+// GOOD: Fully implemented logic with complete error handling
+export function processTransaction(tx: Transaction): TransactionResult {
+  if (!tx.amount || tx.amount <= 0) {
+    throw new ValidationError('Transaction amount must be positive');
+  }
+  if (tx.senderBalance < tx.amount) {
+    throw new InsufficientFundsError(tx.senderId, tx.amount);
+  }
+  return {
+    status: 'ok',
+    transactionId: tx.id,
+    newBalance: tx.senderBalance - tx.amount,
+  };
+}
+```
+
+---
+
+## Example 3: Mandatory Proof-of-Work Invariant
+
+### Anti-pattern: Claiming Task Complete Without Evidence
+
+```text
+BAD: "I have updated the authentication handler. The code looks correct and is ready to merge."
+```
+
+### Best practice: ContextOS Standard (Verified with Automated Gates)
+
+```bash
+# GOOD: Run test suite, staged scanner, and consistency checks
+npm test
+contextos scan --staged --enforce
+node .agents/ctx.js validate
+```

package/.agents/core/skills/gemini-precision/SKILL.md

@@ -51,6 +51,7 @@ Activate whenever:
   1. Run the project validator or compiler (`node .agents/ctx.js validate`, `tsc --noEmit`, etc.).
   2. Run unit and integration tests (`npm test`, `pytest`, etc.).
   3. Run linter and formatting checks (`npm run lint:md`, `eslint`, etc.).
+  4. Run staged security and quality scanner (`contextos scan --staged --enforce`).
 - If a test or validation fails, do not guess: read the exact error trace, fix the root cause, and re-run until green.
 
 ### 4. Surgical Blast Radius Containment
@@ -86,7 +87,7 @@ Activate whenever:
 **Eliminate the "black box" by narrating technical decisions.**
 
 - Avoid executing long, silent chains of tool calls without user visibility.
-- Provide a concise 1–2 sentence transparent status update before key operations:
+- Provide a concise 1-2 sentence transparent status update before key operations:
   - State what was inspected or verified from the code.
   - State the architectural decision made and the immediate next action.
 - Keep narration crisp and actionable without excessive verbosity.

package/.agents/core/skills/gemini-precision/TROUBLESHOOTING.md

@@ -0,0 +1,25 @@
+# gemini-precision Troubleshooting & Common Failure Modes
+
+## 1. Test Failure Investigation (No Guesswork)
+
+- **Symptom**: Test fails during `npm test` after code modifications.
+- **Root Cause**: Trying to patch the code without reading the exact assertion diff.
+- **Fix**: Never guess the fix. View the test file line where assertion failed, inspect expected vs actual output, and resolve the root discrepancy.
+
+## 2. Accidental Staged Secrets or Placeholders
+
+- **Symptom**: `contextos scan --staged --enforce` fails with exit code 1.
+- **Root Cause**: Committed temporary `.env` file or left an unfinished `// TODO: implement later` stub in added lines.
+- **Fix**: Remove or redact the secret before committing. Fully implement the logic or replace the placeholder with an explicit tracked issue rather than committed code stubs.
+
+## 3. Scope Creep and Excessive Blast Radius
+
+- **Symptom**: Unrelated files reformatted or imports reordered across the repository.
+- **Root Cause**: Full-file rewrite instead of targeted surgical replacement.
+- **Fix**: Use targeted chunks that touch only the lines specified in the task plan. Avoid modifying unrelated styling or formatting.
+
+## 4. Forbidden Long Dashes
+
+- **Symptom**: Linter or compliance check flags unicode dashes in text.
+- **Root Cause**: Using typography dashes (`\u2014` or `\u2013`) instead of standard ASCII hyphens.
+- **Fix**: Replace all em-dashes and en-dashes with standard ASCII hyphens (` - `) or appropriate punctuation (parentheses, commas, colons).

package/.agents/core/skills/gemini-precision/skill.yaml

@@ -4,5 +4,7 @@ type: instruction-only
 description: High-precision engineering and execution guardrails optimized for Google Gemini models. Enforces zero-assumption file inspection, complete non-lazy implementations, surgical blast-radius containment, and mandatory proof-of-work execution.
 version: 1.0.0
 resources:
+  - EXAMPLES.md
   - SKILL.md
+  - TROUBLESHOOTING.md
   - VALIDATION.json

package/.agents/core/skills/gstack-roles/SKILL.md

@@ -17,7 +17,7 @@ Activate on every task to declare explicit specialist role and mindset before be
 
 ## Rules & Patterns
 
-Inspired by [Garry Tan's gstack](https://github.com/garrytan/gstack) — shipping 810× more logical code than a solo dev in 2013.
+Inspired by [Garry Tan's gstack](https://github.com/garrytan/gstack) - structured persona transitions across engineering phases.
 
 ## Core Principle
 
@@ -25,13 +25,14 @@ Inspired by [Garry Tan's gstack](https://github.com/garrytan/gstack) — shippin
 
 ## Role Identification Protocol
 
-At the start of each task or major phase switch, declare your role:
+At the start of each task or major phase switch, declare your role using the ContextOS standard format:
 
-```
-[ROLE: <Role Name>] — <One-line description of your mandate for this task>
+```text
+[DOMAIN: <Domain>] [PHASE: <Phase>] [ROLE: <Role Name>]
+Skills loaded: <skill-1>, <skill-2>
 ```
 
-> **Anti-Spam Invariant**: Declare this role **strictly once per phase**. Never prefix intermediate tool calls, file operations, or step updates with role tags.
+> **Anti-Spam Invariant**: Declare this role header **strictly once per phase**. Never prefix intermediate tool calls, file operations, or step updates with role tags.
 
 Then execute ONLY within the constraints of that role.
 
@@ -110,7 +111,7 @@ THINK          PLAN           BUILD          REVIEW         TEST           SHIP
 2. **One role at a time.** Don't mix QA and implementation in the same response.
 3. **Declare before acting.** Always state `[ROLE: X]` before switching modes.
 4. **Escalate correctly.** If a QA finds an architectural problem → escalate to Architect role.
-5. **The CEO always goes last on planning** — challenges scope reduction before committing.
+5. **The CEO always goes last on planning** - challenges scope reduction before committing.
 
 ## Example Usage