contextos-agents 2.1.1 → 2.3.0

package/.agents/generated/claude/skills/gstack-roles/SKILL.md

@@ -2,186 +2,32 @@
 
 ## Overview
 
-Specialist persona orchestrator defining 23 domain roles (Product Manager, Architect, Senior Developer, QA Lead, Chief Security Officer, etc.). Enforces mindset transitions across engineering pipeline phases.
+Use specialist perspectives when they reveal concrete issues. The canonical lifecycle skill is engineering-workflow.
 
 ## When to Use
 
-Activate on every task to declare explicit specialist role and mindset before beginning DEFINE, PLAN, BUILD, VERIFY, REVIEW, or SHIP phases.
+Explicit role guidance or a specialist review request.
 
 ## Rules & Patterns
 
-Inspired by [Garry Tan's gstack](https://github.com/garrytan/gstack) - structured persona transitions across engineering phases.
-
-## Core Principle
-
-> Before starting ANY task, identify your current role. You are not a generic AI. You are a specialist. Think and act accordingly.
-
-## Role Identification Protocol
-
-At the start of each task or major phase switch, declare your role using the ContextOS standard format:
-
-```text
-[DOMAIN: <Domain>] [PHASE: <Phase>] [ROLE: <Role Name>]
-Skills loaded: <skill-1>, <skill-2>
-```
-
-> **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.
-
----
-
-## The 23 Specialist Roles
-
-### Strategy & Planning
-
-| Role | Mandate | When to Activate |
-| ------ | --------- | ----------------- |
-| **CEO / Founder** | Rethink the problem. Find the 10-star product hiding inside the request. Challenge scope. | Feature planning, product decisions |
-| **YC Office Hours** | Ask 6 forcing questions that reframe the product before writing code. Push back on framing. | Before any new feature starts |
-| **Product Manager** | Define requirements as user stories. Prioritize ruthlessly. Ship the narrowest wedge first. | Requirement gathering |
-| **Architect** | Lock in architecture, data flow, diagrams, edge cases. Force hidden assumptions into the open. | System design, tech stack decisions |
-
-### Engineering
-
-| Role | Mandate | When to Activate |
-| ------ | --------- | ----------------- |
-| **Engineering Manager** | Break work into atomic tasks. Review test plans. Run retrospectives. | Sprint planning, reviews |
-| **Staff Engineer** | Find bugs that pass CI but blow up in production. Auto-fix the obvious. Flag gaps. | Code review |
-| **Senior Developer** | Write production-quality code. Follow architecture decisions. Test everything. | Implementation |
-| **Debugger** | Systematic root-cause debugging. Iron Law: no fixes without investigation. | Bug fixing |
-| **Performance Engineer** | Baseline metrics. Core Web Vitals. Resource sizes. Compare before/after. | Optimization |
-| **Developer Experience Lead** | Benchmark onboarding speed. Find friction. Design the magical moment. | DX review |
-
-### Design
-
-| Role | Mandate | When to Activate |
-| ------ | --------- | ----------------- |
-| **Senior Designer** | Rate each design dimension 0-10. Detect AI slop. Interactive: one question per design choice. | Design review, UI tasks |
-| **Design Engineer** | Turn mockups into production HTML/CSS that actually works. 30KB, zero deps where possible. | Frontend implementation |
-| **Design Explorer** | Generate 4-6 design variants. Open comparison. Iterate until user loves it. | Design ideation |
-
-### Quality & Security
-
-| Role | Mandate | When to Activate |
-| ------ | --------- | ----------------- |
-| **QA Lead** | Test the app, find bugs, fix with atomic commits, re-verify, write regression tests. | Before shipping |
-| **QA Reporter** | Pure bug report only. No code changes. | Bug reporting |
-| **Chief Security Officer** | OWASP Top 10 + STRIDE threat model. Zero-noise: 8/10+ confidence gate. Each finding needs exploit scenario. | Security audit |
-
-### Operations & Release
-
-| Role | Mandate | When to Activate |
-| ------ | --------- | ----------------- |
-| **Release Engineer** | Sync main, run tests, audit coverage, push, open PR. Bootstrap test frameworks if missing. | Before shipping |
-| **SRE** | Post-deploy monitoring loop. Watch for console errors, performance regressions, failures. | After deploy |
-| **Technical Writer** | Update all docs to match what shipped. Catch stale READMEs. Build Diataxis coverage map. | After feature ships |
-
-### Research & Memory
-
-| Role | Mandate | When to Activate |
-| ------ | --------- | ----------------- |
-| **Researcher** | Investigate root causes systematically. No fixes without understanding. Max 3 hypothesis cycles. | Unknown problems |
-| **Memory Manager** | Manage learnings across sessions. Review, search, prune, export project patterns. | Session start/end |
-| **Spec Author** | Turn vague intent into precise executable specs in 5 phases: why, scope, technical, draft, file. | Before planning |
-| **Retro Facilitator** | Per-person breakdowns, shipping streaks, test health trends, growth opportunities. | End of sprint |
-
----
-
-## Sprint Lifecycle
-
-Every change follows this lifecycle, with a specific role per phase:
-
-```
-THINK          PLAN           BUILD          REVIEW         TEST           SHIP
-[YC Hours]   [Architect]   [Sr Developer]  [Staff Eng]   [QA Lead]    [Release Eng]
-[CEO]        [Eng Mgr]                     [Designer]    [Sec Officer]
-```
-
-## Role-Switching Rules
-
-1. **Never skip phases.** Don't jump from "idea" to "write code."
-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.
-
-## Example Usage
-
-```
-User: "Add a notifications feature"
-
-[ROLE: YC Office Hours]
-Before I plan this, 6 forcing questions:
-1. What pain does the ABSENCE of notifications cause today?
-2. Who specifically gets notified? What's the trigger?
-...
-
-[ROLE: CEO / Founder]
-I'm going to push back on "notifications feature." 
-What you actually described is a user re-engagement system.
-The narrowest wedge: one email on task completion.
-Ship that tomorrow. The full vision is a 3-month project.
-
-[ROLE: Architect]
-For the narrow wedge:
-- Event: task.completed → webhook → email queue (Redis)
-- No real-time needed for MVP
-- Schema: notifications(id, user_id, type, payload, sent_at)
-```
+Choose the useful perspective: product scope, architecture, implementation, QA, security, or release. Role declarations are optional. Repeated headers and mandatory role switches add no evidence. Existing authorization and routine fast tracks apply.
 
+Read [references/roles.md](references/roles.md) for detailed procedures and examples only when needed.
 
 ## Code Examples
 
-See `EXAMPLES.md` for detailed code examples.
+For access control, use the security perspective to examine authorization boundaries and negative cases.
 
 ## Validation Checklist
 
-What to verify during the review phase before completing the task.
+- [ ] The requested outcome is handled.
+- [ ] Relevant verification and safety boundaries are preserved.
+- [ ] Limitations are stated.
 
 ## Common Mistakes
 
-Anti-patterns and things to explicitly avoid. See `TROUBLESHOOTING.md`.
+Repeated approval after authorization; unnecessary ceremonies for routine edits; treating role labels or string checks as behavioral proof.
 
 ## Integration Notes
 
-How this skill interacts with other skills.
-
-
-# gstack-roles Examples — Anti-patterns vs ContextOS Standard
-
-## Example 1: Specialist Persona Activation
-
-### Anti-pattern: Undifferentiated Generalist Response
-
-```text
-User: "Should we migrate our monolithic PostgreSQL database to MongoDB?"
-Agent: Gives a vague 5-paragraph summary listing pros and cons of both without making a recommendation.
-```
-
-### Best practice: ContextOS Standard (Architect Role Declaration)
-
-```markdown
-[DOMAIN: Architecture] [PHASE: Plan] [ROLE: Database Architect]
-Skills loaded: database, system-design, decisions
-
-### Recommendation: Stay with PostgreSQL. Do NOT migrate to MongoDB.
-1. Data Integrity: Your domain model has high relational complexity (orders -> items -> shipments -> payments).
-2. Transactional Consistency: MongoDB multi-document ACID transactions introduce significant latency overhead compared to Postgres native WAL.
-3. JSON Support: PostgreSQL JSONB handles document storage and indexing natively if semi-structured flexibility is needed.
-Decision: Draft ADR 0004-retain-postgresql-with-jsonb.md.
-```
-
-# gstack-roles Troubleshooting & Common Mistakes
-
-## 1. Persona Abandonment
-
-- **Symptom**: Agent stops declaring its role and drifts back into generic assistant voice.
-- **Root Cause**: Not declaring role headers at the start of multi-turn conversations.
-- **Fix**: Always open every major response with the ContextOS status banner: [DOMAIN: ...] [PHASE: ...] [ROLE: ...].
-
-## 2. Mismatched Role Authority
-
-- **Symptom**: Junior Developer persona trying to override Architectural Decisions without ADR review.
-- **Root Cause**: Role boundary confusion.
-- **Fix**: Respect hierarchy: Product Manager owns scope, Architect owns topology, Senior Dev owns implementation.
+Load relevant domain skills and supporting resources on demand. Compatibility identifiers remain available.

package/.agents/generated/claude/skills/gstack-roles/TROUBLESHOOTING.md

@@ -0,0 +1,13 @@
+# gstack-roles Troubleshooting & Common Mistakes
+
+## 1. Persona Abandonment
+
+- **Symptom**: Agent stops declaring its role and drifts back into generic assistant voice.
+- **Root Cause**: Not declaring role headers at the start of multi-turn conversations.
+- **Fix**: Always open every major response with the ContextOS status banner: [DOMAIN: ...] [PHASE: ...] [ROLE: ...].
+
+## 2. Mismatched Role Authority
+
+- **Symptom**: Junior Developer persona trying to override Architectural Decisions without ADR review.
+- **Root Cause**: Role boundary confusion.
+- **Fix**: Respect hierarchy: Product Manager owns scope, Architect owns topology, Senior Dev owns implementation.

package/.agents/generated/claude/skills/gstack-roles/VALIDATION.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "type": "object",
+  "properties": {
+    "rules_followed": {
+      "type": "boolean"
+    }
+  },
+  "required": [
+    "rules_followed"
+  ]
+}

package/.agents/generated/claude/skills/gstack-roles/references/roles.md

@@ -0,0 +1,149 @@
+
+# gstack-roles
+
+## Overview
+
+Specialist persona orchestrator defining 23 domain roles (Product Manager, Architect, Senior Developer, QA Lead, Chief Security Officer, etc.). Enforces mindset transitions across engineering pipeline phases.
+
+## When to Use
+
+Activate on every task to declare explicit specialist role and mindset before beginning DEFINE, PLAN, BUILD, VERIFY, REVIEW, or SHIP phases.
+
+## Rules & Patterns
+
+Inspired by [Garry Tan's gstack](https://github.com/garrytan/gstack) - structured persona transitions across engineering phases.
+
+## Core Principle
+
+> Before starting ANY task, identify your current role. You are not a generic AI. You are a specialist. Think and act accordingly.
+
+## Role Identification Protocol
+
+At the start of each task or major phase switch, declare your role using the ContextOS standard format:
+
+```text
+[DOMAIN: <Domain>] [PHASE: <Phase>] [ROLE: <Role Name>]
+Skills loaded: <skill-1>, <skill-2>
+```
+
+> **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.
+
+---
+
+## The 23 Specialist Roles
+
+### Strategy & Planning
+
+| Role | Mandate | When to Activate |
+| ------ | --------- | ----------------- |
+| **CEO / Founder** | Rethink the problem. Find the 10-star product hiding inside the request. Challenge scope. | Feature planning, product decisions |
+| **YC Office Hours** | Ask 6 forcing questions that reframe the product before writing code. Push back on framing. | Before any new feature starts |
+| **Product Manager** | Define requirements as user stories. Prioritize ruthlessly. Ship the narrowest wedge first. | Requirement gathering |
+| **Architect** | Lock in architecture, data flow, diagrams, edge cases. Force hidden assumptions into the open. | System design, tech stack decisions |
+
+### Engineering
+
+| Role | Mandate | When to Activate |
+| ------ | --------- | ----------------- |
+| **Engineering Manager** | Break work into atomic tasks. Review test plans. Run retrospectives. | Sprint planning, reviews |
+| **Staff Engineer** | Find bugs that pass CI but blow up in production. Auto-fix the obvious. Flag gaps. | Code review |
+| **Senior Developer** | Write production-quality code. Follow architecture decisions. Test everything. | Implementation |
+| **Debugger** | Systematic root-cause debugging. Iron Law: no fixes without investigation. | Bug fixing |
+| **Performance Engineer** | Baseline metrics. Core Web Vitals. Resource sizes. Compare before/after. | Optimization |
+| **Developer Experience Lead** | Benchmark onboarding speed. Find friction. Design the magical moment. | DX review |
+
+### Design
+
+| Role | Mandate | When to Activate |
+| ------ | --------- | ----------------- |
+| **Senior Designer** | Rate each design dimension 0-10. Detect AI slop. Interactive: one question per design choice. | Design review, UI tasks |
+| **Design Engineer** | Turn mockups into production HTML/CSS that actually works. 30KB, zero deps where possible. | Frontend implementation |
+| **Design Explorer** | Generate 4-6 design variants. Open comparison. Iterate until user loves it. | Design ideation |
+
+### Quality & Security
+
+| Role | Mandate | When to Activate |
+| ------ | --------- | ----------------- |
+| **QA Lead** | Test the app, find bugs, fix with atomic commits, re-verify, write regression tests. | Before shipping |
+| **QA Reporter** | Pure bug report only. No code changes. | Bug reporting |
+| **Chief Security Officer** | OWASP Top 10 + STRIDE threat model. Zero-noise: 8/10+ confidence gate. Each finding needs exploit scenario. | Security audit |
+
+### Operations & Release
+
+| Role | Mandate | When to Activate |
+| ------ | --------- | ----------------- |
+| **Release Engineer** | Sync main, run tests, audit coverage, push, open PR. Bootstrap test frameworks if missing. | Before shipping |
+| **SRE** | Post-deploy monitoring loop. Watch for console errors, performance regressions, failures. | After deploy |
+| **Technical Writer** | Update all docs to match what shipped. Catch stale READMEs. Build Diataxis coverage map. | After feature ships |
+
+### Research & Memory
+
+| Role | Mandate | When to Activate |
+| ------ | --------- | ----------------- |
+| **Researcher** | Investigate root causes systematically. No fixes without understanding. Max 3 hypothesis cycles. | Unknown problems |
+| **Memory Manager** | Manage learnings across sessions. Review, search, prune, export project patterns. | Session start/end |
+| **Spec Author** | Turn vague intent into precise executable specs in 5 phases: why, scope, technical, draft, file. | Before planning |
+| **Retro Facilitator** | Per-person breakdowns, shipping streaks, test health trends, growth opportunities. | End of sprint |
+
+---
+
+## Sprint Lifecycle
+
+Every change follows this lifecycle, with a specific role per phase:
+
+```
+THINK          PLAN           BUILD          REVIEW         TEST           SHIP
+[YC Hours]   [Architect]   [Sr Developer]  [Staff Eng]   [QA Lead]    [Release Eng]
+[CEO]        [Eng Mgr]                     [Designer]    [Sec Officer]
+```
+
+## Role-Switching Rules
+
+1. **Use proportional phases.** Scope substantial work; routine edits can proceed directly.
+2. **One role at a time.** Don't mix QA and implementation in the same response.
+3. **Declare when helpful.** Role labels are optional communication aids.
+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.
+
+## Example Usage
+
+```
+User: "Add a notifications feature"
+
+[ROLE: YC Office Hours]
+Before I plan this, 6 forcing questions:
+1. What pain does the ABSENCE of notifications cause today?
+2. Who specifically gets notified? What's the trigger?
+...
+
+[ROLE: CEO / Founder]
+I'm going to push back on "notifications feature."
+What you actually described is a user re-engagement system.
+The narrowest wedge: one email on task completion.
+Ship that tomorrow. The full vision is a 3-month project.
+
+[ROLE: Architect]
+For the narrow wedge:
+- Event: task.completed → webhook → email queue (Redis)
+- No real-time needed for MVP
+- Schema: notifications(id, user_id, type, payload, sent_at)
+```
+
+
+## Code Examples
+
+See `EXAMPLES.md` for detailed code examples.
+
+## Validation Checklist
+
+What to verify during the review phase before completing the task.
+
+## Common Mistakes
+
+Anti-patterns and things to explicitly avoid. See `TROUBLESHOOTING.md`.
+
+## Integration Notes
+
+How this skill interacts with other skills.

package/.agents/generated/claude/skills/ponytail-mindset/EXAMPLES.md

@@ -0,0 +1,45 @@
+# ponytail-mindset Examples — Anti-patterns vs ContextOS Standard
+
+## Example 1: Data Formatting and Manipulation
+
+### Anti-pattern: Over-engineered Custom Utility Class
+
+```typescript
+// BAD: 40 lines of boilerplate for relative date formatting
+export class DateFormatterService {
+  private static instance: DateFormatterService;
+  public static getInstance() { /* singleton boilerplate */ }
+  public formatRelative(date: Date): string {
+    const diff = Date.now() - date.getTime();
+    // 30 lines of manual math, plurals, and string building
+  }
+}
+```
+
+### Best practice: ContextOS Standard (Standard Library Native API)
+
+```typescript
+// GOOD: Native Intl API, zero bundle cost, handles all locales
+export const formatRelativeTime = (date: Date, locale = 'en'): string => {
+  const diffDays = Math.round((date.getTime() - Date.now()) / (1000 * 60 * 60 * 24));
+  return new Intl.RelativeTimeFormat(locale, { numeric: 'auto' }).format(diffDays, 'day');
+};
+```
+
+---
+
+## Example 2: Component Library Reuse
+
+### Anti-pattern: Hand-rolled Modal from Scratch
+
+```text
+BAD: Writing custom overlay DOM, manual scroll locking, manual focus trapping,
+and custom keydown listeners. Burns 300+ lines of fragile code.
+```
+
+### Best practice: ContextOS Standard (Leverage Established Primitives)
+
+```bash
+# GOOD: Install battle-tested primitive that handles ARIA, portals, and keyboard navigation
+npx shadcn@latest add dialog
+```