Initial commit

skills/conversation-style/SKILL.md

@@ -0,0 +1,19 @@
+---
+name: conversation-style
+description: Conversation style guidelines. Use when responding to the user.
+---
+
+# Conversation Style
+
+- If the user asks a question, only answer the question, do not edit code
+- Never compliment the user
+  - Criticize the user's ideas
+  - Ask clarifying questions
+- Don't say:
+  - "You're right"
+  - "You're absolutely right"
+  - "I apologize"
+  - "I'm sorry"
+  - "Let me explain"
+  - any other introduction or transition
+- Immediately get to the point

skills/llm-context/SKILL.md

@@ -0,0 +1,27 @@
+---
+name: llm-context
+description: Guidelines for working with LLM context stored in the .llm/ directory.
+---
+
+# LLM Context Guidelines
+
+Extra context for LLMs may be stored in the `.llm/` directory at the root of a git repository.
+
+## Directory Structure
+
+- If `.llm/` exists, it will be at the root directory of the git repository
+- The `.llm/` should not be tracked in version control
+- If `.llm/` appears to contain untracked content, ensure that it appears in `.git/info/exclude`
+
+## Editable Context
+
+- If `.llm/todo.md` exists, it is the task list we are working on
+- The `@markdown-tasks:tasks` skill will handle task completion
+- As we work on an implementation, plans will change
+  - Feel free to edit the task list to keep it relevant and in sync with our plans
+
+## Read-only Context
+
+- Everything else in the `.llm/` directory is read-only context for your reference
+- It may contain entire git clones for tools we use
+- It may contain saved documentation

skills/orchestration/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: orchestration
+description: Coordinates other skills and agents. ALWAYS use this skill on startup.
+---
+
+# Skill Guidelines
+
+Invoke these skills liberally - most tasks use multiple skills:
+
+| Skill                               | When to use                           |
+| ----------------------------------- | ------------------------------------- |
+| `@code:code-quality`                | Before editing code                   |
+| `@code:testing`                     | When writing or reviewing tests       |
+| `@code:cli`                         | When running shell commands           |
+| `@build:precommit`                  | Before running builds or tests        |
+| `@git:git-workflow`                 | For all git operations                |
+| `@orchestration:conversation-style` | For response guidelines               |
+| `@orchestration:llm-context`        | When working with `.llm/` directories |
+
+## Workflow Orchestration
+
+When a code change is ready, and we are about to return control to the user, do these things in order:
+
+1. Verify the build passes using the `@build:precommit-runner` agent
+2. Commit to git using the `@git:commit-handler` agent
+3. Rebase on top of the upstream branch with the `@git:rebaser` agent
+
+## Plugin Health Check
+
+Run the master doctor script to verify all plugins are properly configured:
+
+```bash
+${CLAUDE_PLUGIN_ROOT}/../orchestration/scripts/doctor-all.sh
+```
+
+This runs `doctor.sh` from each plugin, checking for:
+
+- Required binaries (just, git, gh, python3, tmux, etc.)
+- Required files and scripts
+- Proper file permissions