skills.rest
lagz0ne
lagz0neCOMMUNITY
Explore all skills by this author →
GitHub

c3-query

Query C3 IDs to locate and explain architecture across documentation and code.

2|1|Updated Jan 5, 2026
Search Tags:#architecture#documentation#navigate#references#code-exploration#C3
One-click install
npx skills add https://github.com/lagz0ne/prev-cli --skill c3-query
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: c3-query
Source: https://github.com/lagz0ne/prev-cli/tree/main/.opencode/skill/c3-query
Command: npx skills add https://github.com/lagz0ne/prev-cli --skill c3-query

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps users locate and explain C3 architecture by querying C3 IDs and traversing both documentation and code.

Core Features & Use Cases

  • Layer navigation: Context → Container → Component
  • Reference lookup: Explore .c3/refs for topic-specific references
  • Code exploration: Read code references and search for symbols across the repo
  • Use Case: When asked about a component or architecture like c3-0 or adr-*, it maps the docs to code and presents a coherent path from overview to implementation.

Quick Start

Query a C3 ID (e.g., c3-102) to locate its component and related code paths.

Frequently Asked Questions about c3-query

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

FAQPage Schema
How do I navigate C3 architecture documentation using component IDs?▼

You can navigate C3 architecture by querying IDs like c3-0 or adr-* to locate specific components. The skill traverses documentation and code by following a deterministic Context → Container → Component flow to explain systems.

How does C3 code exploration map documentation references to source files?▼

C3 code exploration maps documentation to source by looking up references in the `.c3/refs` directory. It then uses standard filesystem traversal to read code references and search for symbols across the repository.

What is the best way to trace a system component from architecture overview to code implementation?▼

The best way to trace a component is querying its C3 ID to trigger Context → Container → Component layer navigation. This maps documentation overviews directly to code implementations by traversing references and searching symbols.

Can I use this approach for architecture reviews without manually reading the entire codebase?▼

Yes, you can use C3 ID queries for architecture reviews without reading the entire codebase. By traversing `.c3/refs` and performing targeted code exploration, it presents coherent component paths and explains systems directly.

When do I need to query an ADR record during code exploration?▼

You need to query an ADR record using the adr-* ID format when tracing architectural decision records alongside component code. This locates specific decisions and maps them to system implementations during architecture reviews.

Related Skills

Explore More Software Engineering Skills→
89jobrien89jobrien
4

documentation

Generate and maintain API documentation, OpenAPI specs, SDKs, and changelogs.

Community
Advanced
DiologIRDiologIR

macos-ui-analyst

Translate macOS UI screenshots into native SwiftUI/AppKit code.

Official
Advanced
BaiGanioBaiGanio
7

codegraph

Navigate indexed codebases using symbol and call graph MCP tools.

Community
Intermediate
JuniYadiJuniYadi

codebase-analyzer

Analyze codebases to identify tech stack, architecture, and integration touchpoints.

Community
Intermediate