@leejungkiin/awkit 1.4.3 → 1.5.1

package/skill-packs/superpowers/skills/writing-skills/examples/anti-rationalization.md

@@ -0,0 +1,75 @@
+# Bulletproofing Skills Against Rationalization
+
+Skills that enforce discipline need to resist rationalization. Agents are smart and will find loopholes under pressure.
+
+## Close Every Loophole Explicitly
+
+Don't just state the rule — forbid specific workarounds:
+
+```markdown
+# ❌ BAD
+Write code before test? Delete it.
+
+# ✅ GOOD
+Write code before test? Delete it. Start over.
+
+**No exceptions:**
+- Don't keep it as "reference"
+- Don't "adapt" it while writing tests
+- Don't look at it
+- Delete means delete
+```
+
+## Address "Spirit vs Letter" Arguments
+
+Add foundational principle early:
+
+```markdown
+**Violating the letter of the rules is violating the spirit of the rules.**
+```
+
+This cuts off entire class of "I'm following the spirit" rationalizations.
+
+## Build Rationalization Table
+
+Capture rationalizations from baseline testing. Every excuse agents make goes in the table:
+
+```markdown
+| Excuse | Reality |
+|--------|---------|
+| "Too simple to test" | Simple code breaks. Test takes 30 seconds. |
+| "I'll test after" | Tests passing immediately prove nothing. |
+| "Tests after achieve same goals" | Tests-after = "what does this do?" Tests-first = "what should this do?" |
+```
+
+## Create Red Flags List
+
+Make it easy for agents to self-check:
+
+```markdown
+## Red Flags - STOP and Start Over
+- Code before test
+- "I already manually tested it"
+- "Tests after achieve the same purpose"
+- "It's about spirit not ritual"
+- "This is different because..."
+
+**All of these mean: Delete code. Start over with TDD.**
+```
+
+## Anti-Patterns
+
+### ❌ Narrative Example
+"In session 2025-10-03, we found empty projectDir caused..."
+**Why bad:** Too specific, not reusable
+
+### ❌ Multi-Language Dilution
+example-js.js, example-py.py, example-go.go
+**Why bad:** Mediocre quality, maintenance burden
+
+### ❌ Code in Flowcharts
+**Why bad:** Can't copy-paste, hard to read
+
+### ❌ Generic Labels
+helper1, helper2, step3, pattern4
+**Why bad:** Labels should have semantic meaning

package/skill-packs/superpowers/skills/writing-skills/examples/cso-optimization.md

@@ -0,0 +1,67 @@
+# Antigravity Search Optimization (CSO)
+
+**Critical for discovery:** Future Antigravity needs to FIND your skill.
+
+## 1. Rich Description Field
+
+**Purpose:** Antigravity reads description to decide which skills to load. Make it answer: "Should I read this skill right now?"
+
+**Format:** Start with "Use when..." to focus on triggering conditions.
+
+**CRITICAL: Description = When to Use, NOT What the Skill Does**
+
+The description should ONLY describe triggering conditions. Do NOT summarize the skill's process/workflow.
+
+**Why this matters:** Testing revealed that when a description summarizes the skill's workflow, Antigravity may follow the description instead of reading the full skill content. A description saying "code review between tasks" caused Antigravity to do ONE review, even though the skill's flowchart clearly showed TWO reviews.
+
+```yaml
+# ❌ BAD: Summarizes workflow
+description: Use when executing plans - executes tasks sequentially with code review between tasks
+
+# ✅ GOOD: Just triggering conditions
+description: Use when executing implementation plans with independent tasks in the current session
+```
+
+**Content:**
+- Use concrete triggers, symptoms, and situations
+- Describe the _problem_ not _language-specific symptoms_
+- Keep triggers technology-agnostic unless skill is technology-specific
+- Write in third person
+- **NEVER summarize the skill's process or workflow**
+
+## 2. Keyword Coverage
+
+Use words Antigravity would search for:
+- Error messages: "Hook timed out", "ENOTEMPTY", "race condition"
+- Symptoms: "flaky", "hanging", "zombie", "pollution"
+- Synonyms: "timeout/hang/freeze", "cleanup/teardown/afterEach"
+- Tools: Actual commands, library names, file types
+
+## 3. Descriptive Naming
+
+**Use active voice, verb-first:**
+- ✅ `creating-skills` not `skill-creation`
+- ✅ `condition-based-waiting` not `async-test-helpers`
+- Gerunds (-ing) work well for processes
+
+## 4. Token Efficiency (Critical)
+
+**Target word counts:**
+- getting-started workflows: <150 words each
+- Frequently-loaded skills: <200 words total
+- Other skills: <500 words
+
+**Techniques:**
+- Move details to tool help (`--help`)
+- Use cross-references (not repeated instructions)
+- Compress examples
+- Eliminate redundancy
+
+## 5. Cross-Referencing Other Skills
+
+- ✅ `**Required skill:** test-driven-development`
+- ✅ `See examples/tdd-for-skills.md`
+- ❌ Hardcode platform-specific paths like `.agent/skills/...`
+- ❌ Force-load with `@...` when a plain reference is enough
+
+**Why no forced load:** it burns context before the agent knows whether the deeper file is actually needed.

package/skill-packs/superpowers/skills/writing-skills/examples/tdd-for-skills.md

@@ -0,0 +1,63 @@
+# TDD for Skills: RED-GREEN-REFACTOR + Testing Methodology
+
+## The Iron Law (Same as TDD)
+
+```
+NO SKILL WITHOUT A FAILING TEST FIRST
+```
+
+This applies to NEW skills AND EDITS to existing skills. No exceptions — not for "simple additions", "just adding a section", or "documentation updates".
+
+## RED: Write Failing Test (Baseline)
+
+Run pressure scenario WITHOUT the skill. Document exact behavior:
+- What choices did they make?
+- What rationalizations did they use (verbatim)?
+- Which pressures triggered violations?
+
+## GREEN: Write Minimal Skill
+
+Write skill addressing those specific rationalizations. Don't add extra content for hypothetical cases.
+
+Run same scenarios WITH skill. Agent should now comply.
+
+## REFACTOR: Close Loopholes
+
+Agent found new rationalization? Add explicit counter. Re-test until bulletproof.
+
+If you need a deeper validation harness, keep it in a separate reference file instead of inflating `SKILL.md`.
+
+---
+
+## Testing All Skill Types
+
+### Discipline-Enforcing Skills (rules/requirements)
+- Test with: Academic questions, pressure scenarios, combined pressures
+- Success: Agent follows rule under maximum pressure
+
+### Technique Skills (how-to guides)
+- Test with: Application scenarios, variation scenarios, missing info tests
+- Success: Agent successfully applies technique to new scenario
+
+### Pattern Skills (mental models)
+- Test with: Recognition scenarios, application, counter-examples
+- Success: Agent correctly identifies when/how to apply pattern
+
+### Reference Skills (documentation/APIs)
+- Test with: Retrieval scenarios, application, gap testing
+- Success: Agent finds and correctly applies reference information
+
+---
+
+## Common Rationalizations for Skipping Testing
+
+| Excuse | Reality |
+|--------|---------|
+| "Skill is obviously clear" | Clear to you ≠ clear to other agents. Test it. |
+| "It's just a reference" | References can have gaps. Test retrieval. |
+| "Testing is overkill" | Untested skills have issues. Always. |
+| "I'll test if problems emerge" | Problems = agents can't use skill. Test BEFORE. |
+| "Too tedious to test" | Less tedious than debugging bad skill in production. |
+| "I'm confident it's good" | Overconfidence guarantees issues. Test anyway. |
+
+**All of these mean: Test before deploying. No exceptions.**

package/skills/CATALOG.md

@@ -1,7 +1,7 @@
 # 📋 AWF Skill Catalog
 
-> Classification of all skills by type, trigger, and priority.
-> Updated: 2026-03-06
+> Classification of core runtime skills and optional packs.
+> Updated: 2026-04-02
 
 ---
 
@@ -9,60 +9,65 @@
 
 | Type | Description | Example |
 |------|-------------|---------|
-| `auto` | Always active, runs silently without user command | `orchestrator`, `memory-sync` |
+| `auto` | Always active, runs silently without user command | `orchestrator`, `nm-memory-sync` |
 | `manual` | User must explicitly invoke via `/command` or keyword | `brainstorm-agent`, `ios-engineer` |
 
 ---
 
-## Active Skills
-
-| # | Skill | Type | Trigger | Priority | Version | Status |
-|---|-------|------|---------|----------|---------|--------|
-| 1 | `orchestrator` | `auto` | Always (first) | 1 | 2.1.0 | ✅ Active |
-| 2 | `awf-session-restore` | `auto` | Session start | 2 | — | ✅ Active |
-| 3 | `memory-sync` | `auto` | Always | 3 | 2.2.0 | ✅ Active |
-| 4 | `symphony-orchestrator` | `auto` | Always | 4 | 1.0.0 | ✅ Active |
-| 5 | `brainstorm-agent` | `manual` | `/brainstorm`, keywords | 5 | 1.0.0 | ✅ Active |
-| 6 | `awf-error-translator` | `auto` | Error detected | 6 | — | ✅ Active |
-| 7 | `awf-adaptive-language` | `auto` | Always | 7 | — | ✅ Active |
-| 8 | `ios-engineer` | `manual` | iOS tasks | — | — | ✅ Active |
-| 9 | `smali-to-kotlin` | `manual` | `/reverse-android` | 8 | — | ✅ Active |
-| 10 | `smali-to-swift` | `manual` | `/reverse-ios` | 9 | — | ✅ Active |
-| 11 | `awf-context-help` | `auto` | `/help`, stuck | — | — | ✅ Active |
-| 12 | `auto-save` | `auto` | Session end | — | — | ✅ Background |
-| 13 | `awf-version-tracker` | `auto` | Skill changes | — | — | ✅ Background |
-| 14 | `module-spec-writer` | `auto` | Gate 1.5 check fail | 1.5 | 1.0.0 | ✅ Active |
-| 15 | `spec-gate` | `auto` | Gate 2 check fail | 2 | 1.0.0 | ✅ Active |
-| 16 | `visual-design-gate` | `auto` | Gate 2.5 check fail | 2.5 | 1.0.0 | ✅ Active |
-| 17 | `trello-sync` | `auto` | Always | 2 | 3.0.0 | ✅ Active |
+## Default Runtime Profile (`awkit install`)
 
----
+`awkit install` now installs a lean runtime profile instead of the full source skill library.
 
-## Quality & Discipline Skills (Superpowers-Inspired)
+### Core Lifecycle & Coordination
 
-> Skills ported and adapted from [obra/superpowers](https://github.com/obra/superpowers) framework.
-> Integrated into AWKit with NeuralMemory + Symphony extensions.
+- `orchestrator`
+- `symphony-orchestrator`
+- `awf-session-restore`
+- `nm-memory-sync`
+- `symphony-enforcer`
+- `trello-sync`
 
-| # | Skill | Type | Trigger | Priority | Status |
-|---|-------|------|---------|----------|--------|
-| 14 | `verification-gate` | `auto` | Task completion, commit, deploy | 1 | ✅ Active |
-| 15 | `systematic-debugging` | `auto` | `/debug`, error detected, test failures | 2 | ✅ Active |
-| 16 | `code-review` | `auto` | Task completion, before merge | 3 | ✅ Active |
-| 17 | `writing-skills` | `manual` | Creating/modifying skills | — | ✅ Active |
+### Planning & Execution
 
+- `brainstorm-agent`
+- `module-spec-writer`
+- `spec-gate`
+- `visual-design-gate`
+- `single-flow-task-execution`
 
----
+### Quality & Debugging
+
+- `systematic-debugging`
+- `verification-gate`
+- `code-review`
+- `gitnexus-intelligence`
 
-## NeuralMemory Skill Pack (Optional Upgrade)
+### Meta / Self-Evolution
+
+- `writing-skills`
+- `skill-creator`
+- `awf-version-tracker`
+- `auto-save`
+- `awf-adaptive-language`
+- `awf-context-help`
+- `awf-error-translator`
+- `gemini-conductor`
+- `codex-conductor`
+- `telegram-notify`
+- `ship-to-code`
+
+---
 
-When NeuralMemory is installed, these skills provide enhanced capabilities:
+## Optional Packs
 
-| # | Skill | Type | Replaces | Trigger |
-|---|-------|------|----------|---------|
-| 1 | `nm-memory-sync` | `auto` | `memory-sync` | Session start, debug, errors |
-| 2 | `nm-memory-intake` | `manual` | — | `/memory-intake` |
-| 3 | `nm-memory-audit` | `manual` | — | `/memory-audit` |
-| 4 | `nm-memory-evolution` | `manual` | — | `/memory-evolution` |
+| Pack | Purpose |
+|------|---------|
+| `mobile-ios` | iOS, SwiftUI, Xcode, reverse engineering |
+| `mobile-android` | Android, Kotlin, Compose, AdMob, APK analysis |
+| `marketing` | ASO, App Store marketing, analytics, growth |
+| `creator-studio` | Sprites, LucyLab TTS, short-form video workflows |
+| `neural-memory` | Memory audit, intake, evolution, extra workflows |
+| `superpowers` | Additional execution/TDD/reference skills ported from Superpowers |
 
 ---
 
@@ -71,7 +76,7 @@ When NeuralMemory is installed, these skills provide enhanced capabilities:
 Skills marked with self-evolution have a `## Learnings` section that accumulates insights:
 
 - ✅ `orchestrator` — routing improvements
-- ✅ `memory-sync` — trigger pattern refinements
+- ✅ `nm-memory-sync` — trigger pattern refinements
 - ✅ `symphony-orchestrator` — task management optimizations
 
 ---