oliver-kriska/claude-elixir-phoenix / targets/amp/skills/compound-docs
compound-docs
VerifiedSearchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
| references/resolution-template.md | markdown | 2.8 KB |
| references/schema.md | markdown | 2.8 KB |
references/resolution-template.md
View on GitHub# Resolution Template
Use this template when creating solution documentation in `.claude/solutions/`.
## Filename Convention
```
{sanitized-symptom}-{module}-{YYYYMMDD}.md
```
- Lowercase, hyphen-separated
- Special characters removed
- Truncated under 80 characters
- Example: `association-not-loaded-accounts-20251201.md`
## Full Template
````markdown
---
module: "{Module or context name}"
date: "{YYYY-MM-DD}"
problem_type: {enum from schema}
component: {enum from schema}
symptoms:
- "{Observable symptom 1}"
- "{Observable symptom 2}"
root_cause: {enum from schema}
severity: {critical|high|medium|low}
tags: [{tag1}, {tag2}, {tag3}]
---
# {Descriptive Title}
## Symptoms
What was observed. Include:
- Error messages (exact text)
- Unexpected behavior description
- Where it manifested (which LiveView, which context, which test)
## Investigation
What was tried and what happened:
1. **Hypothesis 1**: {what you thought} — {result}
2. **Hypothesis 2**: {what you thought} — {result}
3. **Root cause found**: {the actual cause}
## Root Cause
Detailed explanation of WHY this happened. Connect to the
underlying Elixir/Phoenix concept.
```elixir
# The problematic code
problematic_code()
```
## Solution
The fix that resolved it.
```elixir
# The working code
fixed_code()
```
### Files Changed
- `lib/my_app/accounts.ex:42` — Added preload
- `test/my_app/accounts_test.exs:15` — Added test for preload
## Prevention
How to prevent this from recurring:
- [ ] Add to Iron Laws? (if foundational pattern)
- [ ] Add to agent checks? (if detectable by reviewer)
- [ ] Add to test patterns? (if testable)
- Specific guidance: "{actionable advice}"
## Related
- `.claude/solutions/{related-file}.md` — Similar issue in different context
- Iron Law #{n}: {description} (if applicable)
````
## Category Directories
Create the file in the appropriate subdirectory:
| problem_type | Directory |
|-------------|-----------|
| `build_error` | `build-issues/` |
| `test_failure` | `testing-issues/` |
| `runtime_error` | `phoenix-issues/` |
| `performance_issue` | `performance-issues/` |
| `database_issue` | `ecto-issues/` |
| `security_issue` | `security-issues/` |
| `liveview_bug` | `liveview-issues/` |
| `oban_issue` | `oban-issues/` |
| `otp_issue` | `otp-issues/` |
| `integration_issue` | `phoenix-issues/` |
| `logic_error` | `phoenix-issues/` |
| `deployment_issue` | `deployment-issues/` |
| `iron_law_violation` | mapped by Iron Law domain |
## Quality Checklist
Before saving, verify:
- [ ] YAML frontmatter validates against schema
- [ ] All enum values are exact matches
- [ ] Symptoms are specific (include error text)
- [ ] Root cause explains WHY, not just WHAT
- [ ] Solution includes code examples
- [ ] Prevention has actionable next steps
- [ ] File is in correct category directory
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |