helderberto/agent-skills

zoom-out

Explain code with visual diagrams and analogies.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/helderberto/agent-skills --skill zoom-out

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

Read the code and anything it depends on before explaining. Then, always:

  1. Start with an analogy from everyday life.
  2. Draw an ASCII diagram matching the shape of the thing: flow, sequence between actors, tree/hierarchy, state machine, data structure, or before/after. One concept per diagram — split rather than cram.
  3. Walk through the code step by step.
  4. Highlight a gotcha: a common mistake or misconception.

Conversational tone. Complex concepts get more than one analogy.

Related by task

from this repository

More skills

All skills
helderberto
Community

codebase-design

Shared vocabulary for designing deep modules. Use when designing or improving a module's interface, placing a seam, making code more testable, or when another skill needs it. Don't use for codebase-wide audits (/architecture-audit) or UI components (/frontend-ui-engineering).

1h installs
1
GitHub stars
17
Updated
Oct 19
helderberto
Community

debug

Disciplined diagnosis loop for hard bugs and performance regressions. Use when user says "diagnose" or "debug this", or reports something broken, throwing, failing, or slow. Don't use to build a feature or fix an understood bug test-first (/tdd).

1h installs
1
GitHub stars
17
Updated
Oct 19
helderberto
Community

deps-audit

Check dependencies for known vulnerabilities and staleness. Use when asked to "audit dependencies", "check for vulnerabilities", or check dependency health. Don't use for code quality review.

1h installs
1
GitHub stars
17
Updated
Oct 19
helderberto
Community

frontend-ui-engineering

Front-load UI construction decisions — component boundary and prop API, state placement, required states, responsiveness, accessibility. Use when creating or refactoring a component, page, or design-system primitive. Don't use for pure logic (/tdd), throwaway exploration (/prototype), or auditing finished UI (/a11y-audit).

1h installs
1
GitHub stars
17
Updated
Oct 19