Explain Pattern

Explain code idioms in-place with rule and ADR citations.

1|1|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill explain-pattern
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Explain Pattern
Source: https://github.com/btabaska/simpler-grants-documentation-automation/tree/main/.cursor/skills/skill-explain-pattern
Command: npx skills add https://github.com/btabaska/simpler-grants-documentation-automation --skill explain-pattern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide in-place explanations of code idioms, functions, decorators, hooks, or snippets grounded in project rules and ADRs rather than generic tutorials.

Core Features & Use Cases

  • In-place explanations anchored to governing rules and ADR references.
  • Produces concise 3-5 sentence explanations with citations to the relevant rules and ADRs.
  • Useful during code reviews, onboarding, and pattern validation before reuse.

Quick Start

Provide the target block and an optional question to generate a concise, cited explanation.

Frequently Asked Questions about Explain Pattern

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I explain code patterns with references to project ADRs during a review?

To explain code patterns with ADR references, provide the target block and an optional question. The tool reads the context, identifies the idiom category, and generates a concise explanation with citations to governing rules and ADRs.

What is the best way to validate code idioms before reuse during onboarding?

Validating code idioms before reuse requires checking them against project conventions. This tool produces a 3-5 sentence explanation anchored to documentation and ADR references, ensuring new developers understand pattern governance quickly.

Can I generate in-place explanations for decorators and hooks without generic tutorials?

Yes, you can generate in-place explanations for decorators and hooks without generic tutorials. The tool grounds its output specifically in your project's rules and ADR references rather than broad, generic programming guides.

How do I document a specific code snippet against governing convention rules?

Documenting a snippet against governing convention rules is done by submitting the target block for analysis. The tool searches documentation and ADR references to produce a concise, cited explanation of the code's governance.

Does this approach to explaining code patterns require any specific dependencies?

No specific dependencies are required to explain code patterns with this approach. It operates directly on the provided target block and context to identify the idiom category and search documentation for citations.

When should I not use rule-based citations for code pattern explanations?

Rule-based citations for code pattern explanations are not suitable when your project lacks established convention rules or ADRs. Without governing documentation to search, the tool cannot ground its explanations in project-specific standards.