Results for “file-system”

Systematically explore an unfamiliar codebase and build a reusable architecture summary with file:line evidence, starting from documentation and tracing data flow.

Generates a DESIGN.md file conforming to the Stitch (Google Labs) design.md alpha spec, auto-discovering design tokens and components, then emitting YAML frontmatter and eight standard markdown sections.

Use when compiling a LaTeX paper, debugging LaTeX errors, building a paper PDF, or when a .tex file fails to produce output. Handles engine detection (xelatex vs pdflatex), bibliography systems (biber vs bibtex), and multi-pass compilation.

Turns any long-running domain (business, relationships, health, career, learning, investing) into a local knowledge project with four layers, source tags, immutable snapshots, and a concept library that learns patterns over time.

Produces a human-readable, progressive-disclosure overview of unfamiliar code or a pull request's changes — why it exists (the real problem it solves or goal it serves for the business or a user), and from there what it does, how it flows, and where to start — so you can get up to speed before working on or reviewing it. Use when you want to understand, get oriented in, make sense of, explain, or get up to speed on a chunk of code, a file, a directory, a symbol, or a PR's changes. Writes the overview to a scratch file and changes no code. Does not review code quality or raise findings — use code-review for auditing changes or post-code-review-to-pr for posting them. Does not produce durable feature or system documentation — use project-documentation. Does not assess architecture or structural risk — use architectural-analysis. Does not diagnose bugs or root-cause failures — use investigate. Does not pace a person through the code one step at a time in conversation — use code-walkthrough.

Generates a structured developer-facing markdown document that teaches how a specific feature, module, or piece of functionality works in the codebase. Use this skill whenever the user runs `/teach`, asks "how does X work", "explain the auth flow", "document how payments work", "walk me through the webhook system", or any request to understand and document internal codebase functionality. Also trigger when the user wants to produce onboarding docs, feature walkthroughs, or "how it works" references for developers. Always use this skill even if the user only gives a vague description — use the provided context or file hints to locate the relevant code yourself and build the teaching doc from there. This skill writes for developers reading the codebase — for end-user/customer-facing help docs, use the eli5-features skill instead.