Skip to content
Back to skills

Compound Docs

ASecurity

Searchable Elixir/Phoenix/Ecto solution documentation system with YAML

  • 559 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 5, 2026
developmentgoawstestingdebuggingsecurityperformancedocumentation

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add oliver-kriska/claude-elixir-phoenix --skill compound-docs --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Compound Docs?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Compound Docs
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/oliver-kriska-compound-docs-7cf2c59e/badge)](https://www.skillsdirectory.com/skills/oliver-kriska-compound-docs-7cf2c59e)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: compound-docs
description: Searchable Elixir/Phoenix/Ecto solution documentation system with YAML
  frontmatter. Builds institutional knowledge from solved problems. Use when consulting
  past solutions before investigating new issues.
---

# Compound Docs — Institutional Knowledge Base

Searchable, categorized solution documentation that makes each
debugging session easier than the last.

## Directory Structure

```
.claude/solutions/
├── ecto-issues/
├── liveview-issues/
├── oban-issues/
├── otp-issues/
├── security-issues/
├── testing-issues/
├── phoenix-issues/
├── deployment-issues/
├── performance-issues/
└── build-issues/
```

## Iron Laws

1. **ALWAYS search solutions before investigating** — Check
   `.claude/solutions/` for existing fixes before debugging
2. **YAML frontmatter is MANDATORY** — Every solution needs
   validated metadata per `references/schema.md`
3. **One problem per file** — Never combine multiple solutions
4. **Include prevention** — Every solution documents how to
   prevent recurrence

## Solution File Format

```markdown
---
module: "Accounts"
date: "2025-12-01"
problem_type: runtime_error
component: ecto_schema
symptoms:
  - "Ecto.Association.NotLoaded on user.posts"
root_cause: missing_preload
severity: medium
tags: [preload, association, n-plus-one]
---

# Association NotLoaded on User Posts

## Symptoms
Ecto.Association.NotLoaded raised when accessing user.posts
in UserListLive after filtering.

## Root Cause
Query in Accounts context missing preload for :posts.

## Solution
Added `Repo.preload(:posts)` to `list_users/1`.

## Prevention
Use n1-check skill before shipping list views.
```

## Searching Solutions

Use Grep to search `.claude/solutions/` by symptom (e.g., `NotLoaded`), by tag (e.g., `tags:.*preload`), or by component (e.g., `component: ecto`).

## Integration

- `/skill:phx-compound` creates solution docs here
- `/skill:phx-investigate` searches here before debugging
- `/skill:phx-plan` consults for known risks
- `learn-from-fix` feeds into this system

## References

- `references/schema.md` — YAML frontmatter validation schema
- `references/resolution-template.md` — Full solution template

Files in this skill

  • SKILL.md2.2 KB
  • references/resolution-template.md2.8 KB
  • references/schema.md2.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…