メニュー
Architectural code analysis for Python design quality. Evaluates simplicity (Rich Hickey), functional core/imperative shell (Gary Bernhardt), and coupling (Constantine & Yourdon). Use for design review or architectural assessment of Python code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Find connections between notes and update MOCs. Requires semantic judgment to identify genuine relationships. Use after /extract creates notes, when exploring connections, or when a topic needs synthesis. Triggers on "/connect", "/connect [note]", "find connections", "update MOCs", "connect these notes".
Extract structured knowledge from source material. Two modes — `extract` (default) for comprehensive atomic claim extraction, and `analyze` for design proposals where one impact-analysis note replaces claim decomposition. A relevance filter ("does this change how we build our project?") applies to all modes. For `extract` mode on domain-relevant sources, skip rate must be below 10%. Triggers on "/extract", "/extract [file]", "extract insights", "mine this", "process this".
Add a source file to the processing queue. Checks for duplicates, creates archive folder, moves source from inbox, creates extract task, and updates queue. Triggers on "/seed", "/seed [file]", "queue this for processing".
Interactive knowledge graph analysis. Routes natural language questions to graph scripts, interprets results in domain vocabulary, and suggests concrete actions. Triggers on "/graph", "/graph health", "/graph triangles", "find synthesis opportunities", "graph analysis".
Research a topic and grow your knowledge graph. Uses Exa deep researcher, web search, or basic search to investigate topics, files results with full provenance, and chains to processing pipeline. Triggers on "/learn", "/learn [topic]", "research this", "find out about".
Surface the most valuable next action by combining task stack, queue state, inbox pressure, health, and goals. Recommends one specific action with rationale. Triggers on "/next", "what should I do", "what's next".
| name | decomplect-py |
| description | Architectural code analysis for Python design quality. Evaluates simplicity (Rich Hickey), functional core/imperative shell (Gary Bernhardt), and coupling (Constantine & Yourdon). Use for design review or architectural assessment of Python code. |
Architectural analysis for Python design quality.
/decomplect-py # Run all 3 analyzers in parallel
/decomplect-py --simplicity # Specific analyzer
/decomplect-py --fcis # Specific analyzer
/decomplect-py --coupling # Specific analyzer
| Analyzer | Question |
|---|---|
| simplicity-analyzer | Is this truly simple or just easy? |
| fcis-analyzer | Is pure logic separated from I/O? |
| coupling-analyzer | Are modules well-separated? |
| Pillar | Focus |
|---|---|
| Simplicity | Values over state, decomplected concerns |
| FCIS | Functional core (pure), imperative shell (I/O) |
| Coupling | High cohesion, low coupling |
.py files only)dataclasses(frozen=True) and NamedTuple for immutable values/decomplect - Analysis for TypeScript/Go/Rust/unslopify - Tactical code cleanup