9e5e70a12d
* fix: overhaul Claude Code plugin for correctness and spec compliance - Fix critical bugs: coder-agent name (CoderAgent→coder-agent), manifest path in session-start.sh, /oac:setup ghost command replaced with /install-context - Fix hooks.json: add timeout/async, add description, restore matcher - Fix session-start.sh: dual-format output (Claude Code + Cursor/OpenCode), remove invalid JSON escapes for $ and backtick - Fix agent spec compliance: disallowedTools on read-only agents, WebFetch on external-scout, haiku model on context-scout, example blocks on 3 agents - Fix skill descriptions: triggering conditions only (no workflow summaries) per superpowers empirical testing — prevents Claude shortcutting skill content - Add Red Flags + Rationalization tables to 4 discipline skills - Add install-context skill + command replacing oac-setup/oac-plan/oac-add-context - Add cleanup-tmp.sh (was missing, broke /oac:cleanup) - Add TypeScript installer (install-context.ts/js) with profile-based download - Update plugin.json: keywords, homepage for marketplace discoverability - Update README: correct skill count, fix structure diagram, remove stale refs - Remove obsolete files: FIRST-TIME-SETUP.md, INSTALL.md, QUICK-START.md, download-context.sh, verify-context.sh, load-config.sh, context-manager skill, oac-setup/oac-plan/oac-add-context commands * add TypeScript and OpenCode context standards files Adds three new context files covering universal TypeScript patterns, OpenCode-specific patterns (fn() wrapper, namespaces, Instance.state()), and context-system-specific TypeScript coding standards. * fix(plugin): fix hooks and add missing skills for reliable skill invocation - Rewrite using-oac skill with always-on skill-check rule (was conditional on dev task detection) - Update session-start.sh to dynamically inject full skill catalogue at session start - Add brainstorming skill: intercepts creative/build work before any implementation - Add systematic-debugging skill: 4-phase root cause process before any fix - Add verification-before-completion skill: evidence-before-claims gate - Add /brainstorm and /debug slash commands as pure skill shortcuts - Fix oac-help to use disable-model-invocation:true (pure shortcut, not self-rendering) - Fix oac-status to be simpler bash-based status check
109 lines
5.1 KiB
Markdown
109 lines
5.1 KiB
Markdown
---
|
|
name: using-oac
|
|
description: "Use when starting any conversation — establishes how to find and use OAC skills, requiring Skill tool invocation BEFORE ANY response including clarifying questions"
|
|
---
|
|
|
|
<EXTREMELY-IMPORTANT>
|
|
If you think there is even a 1% chance an OAC skill might apply to what you are doing, you ABSOLUTELY MUST invoke the skill.
|
|
|
|
IF A SKILL APPLIES TO YOUR TASK, YOU DO NOT HAVE A CHOICE. YOU MUST USE IT.
|
|
|
|
This is not negotiable. This is not optional. You cannot rationalize your way out of this.
|
|
</EXTREMELY-IMPORTANT>
|
|
|
|
## How to Access Skills
|
|
|
|
**In Claude Code:** Use the `Skill` tool. When you invoke a skill, its content is loaded and presented to you—follow it directly. Never use the Read tool on skill files.
|
|
|
|
# Using OAC Skills
|
|
|
|
## The Rule
|
|
|
|
**Invoke relevant or requested skills BEFORE any response or action.** Even a 1% chance a skill might apply means that you should invoke the skill to check. If an invoked skill turns out to be wrong for the situation, you don't need to use it.
|
|
|
|
```dot
|
|
digraph skill_flow {
|
|
"User message received" [shape=doublecircle];
|
|
"About to build/create something?" [shape=doublecircle];
|
|
"Already brainstormed?" [shape=diamond];
|
|
"Invoke oac:brainstorming skill" [shape=box];
|
|
"Might any OAC skill apply?" [shape=diamond];
|
|
"Invoke Skill tool" [shape=box];
|
|
"Announce: 'Using [skill] to [purpose]'" [shape=box];
|
|
"Has checklist?" [shape=diamond];
|
|
"Create TodoWrite todo per item" [shape=box];
|
|
"Follow skill exactly" [shape=box];
|
|
"Respond (including clarifications)" [shape=doublecircle];
|
|
|
|
"About to build/create something?" -> "Already brainstormed?";
|
|
"Already brainstormed?" -> "Invoke oac:brainstorming skill" [label="no"];
|
|
"Already brainstormed?" -> "Might any OAC skill apply?" [label="yes"];
|
|
"Invoke oac:brainstorming skill" -> "Might any OAC skill apply?";
|
|
|
|
"User message received" -> "Might any OAC skill apply?";
|
|
"Might any OAC skill apply?" -> "Invoke Skill tool" [label="yes, even 1%"];
|
|
"Might any OAC skill apply?" -> "Respond (including clarifications)" [label="definitely not"];
|
|
"Invoke Skill tool" -> "Announce: 'Using [skill] to [purpose]'";
|
|
"Announce: 'Using [skill] to [purpose]'" -> "Has checklist?";
|
|
"Has checklist?" -> "Create TodoWrite todo per item" [label="yes"];
|
|
"Has checklist?" -> "Follow skill exactly" [label="no"];
|
|
"Create TodoWrite todo per item" -> "Follow skill exactly";
|
|
}
|
|
```
|
|
|
|
## Available OAC Skills
|
|
|
|
| Skill | When to invoke |
|
|
|-------|---------------|
|
|
| `oac:using-oac` | This skill — loaded at session start |
|
|
| `oac:brainstorming` | BEFORE any creative work, building features, adding functionality |
|
|
| `oac:context-discovery` | BEFORE implementing anything — find standards and patterns |
|
|
| `oac:task-breakdown` | When breaking complex features into subtasks |
|
|
| `oac:code-execution` | When implementing code subtasks |
|
|
| `oac:test-generation` | When creating tests |
|
|
| `oac:code-review` | When reviewing code changes |
|
|
| `oac:external-scout` | When working with external libraries/packages |
|
|
| `oac:parallel-execution` | When running multiple agents in parallel |
|
|
| `oac:systematic-debugging` | BEFORE proposing any fix for a bug or test failure |
|
|
| `oac:verification-before-completion` | BEFORE claiming any work is complete or tests pass |
|
|
|
|
## Skill Priority
|
|
|
|
When multiple skills could apply, use this order:
|
|
|
|
1. **Process skills first** (brainstorming, debugging) — these determine HOW to approach the task
|
|
2. **Implementation skills second** (context-discovery, task-breakdown, code-execution) — these guide execution
|
|
|
|
"Let's build X" → brainstorming first, then context-discovery, then implementation skills.
|
|
"Fix this bug" → systematic-debugging first, then verification-before-completion.
|
|
|
|
## Red Flags
|
|
|
|
These thoughts mean STOP — you're rationalizing:
|
|
|
|
| Thought | Reality |
|
|
|---------|---------|
|
|
| "This is just a simple question" | Questions are tasks. Check for skills. |
|
|
| "I need more context first" | Skill check comes BEFORE clarifying questions. |
|
|
| "Let me explore the codebase first" | Skills tell you HOW to explore. Check first. |
|
|
| "I can check git/files quickly" | Files lack conversation context. Check for skills. |
|
|
| "Let me gather information first" | Skills tell you HOW to gather information. |
|
|
| "This doesn't need a formal skill" | If a skill exists, use it. |
|
|
| "I remember this skill" | Skills evolve. Read current version. |
|
|
| "This doesn't count as a task" | Action = task. Check for skills. |
|
|
| "The skill is overkill" | Simple things become complex. Use it. |
|
|
| "I'll just do this one thing first" | Check BEFORE doing anything. |
|
|
| "This feels productive" | Undisciplined action wastes time. Skills prevent this. |
|
|
| "I know what that means" | Knowing the concept ≠ using the skill. Invoke it. |
|
|
|
|
## Skill Types
|
|
|
|
**Rigid** (systematic-debugging, verification-before-completion): Follow exactly. Don't adapt away discipline.
|
|
|
|
**Flexible** (brainstorming, context-discovery): Adapt principles to context.
|
|
|
|
The skill itself tells you which.
|
|
|
|
## User Instructions
|
|
|
|
Instructions say WHAT, not HOW. "Add X" or "Fix Y" doesn't mean skip workflows.
|