Explorar skills

Use this skill for any architecture, system design, or major technical decision task. Triggers on: "design the system", "architecture for", "how should we structure", "ADR", "architecture decision", "data model", "API design", "system diagram", "technical design", "non-functional requirements", "how should this be built", "what pattern should we use", "scalability", "integration design". Use befor

Run the repo's make targets in dependency order (setup → lint → test → end-to-end) and verify each command's terminal output against its `logs/dev-<ts>-<cmd>.log` archive. Supports a full audit and a fast variant. Use whenever the user wants to validate the toolchain is clean, run lint+test locally before pushing, or reconcile terminal output against the dev-runner log archives — phrasings like "r

Incorporate architectural constraints and technical debt into product prioritization decisions. Use this skill when a team needs to balance feature work with technical investment.

Maintain the Zensical-powered documentation site — nav ordering in zensical.toml, the docs GitHub Pages workflow, CSS and JS assets, and link/anchor integrity across docs/**/*.md. Sibling of /techne:docsync (which only verifies prose claims against code). Use when the user wants the site itself audited — config, deploy pipeline, theming, assets, cross-page links — rather than content accuracy.

Raw mechanical interfaces fusing Swiss typographic print with military terminal aesthetics. Rigid grids, extreme type scale contrast, utilitarian color, analog degradation effects. For data-heavy dashboards, portfolios, or editorial sites that need to feel like declassified blueprints.

Analyze funnel drop-off, retention curves, and cohort behavior to identify problems and opportunities. Use this skill when a team has data and needs to understand user behavior patterns.

Trigger on "search my memory", "look up in my memory", "recall from my notes", "second brain", "thinking partner", "what should I learn today", "connect my ideas", "show my knowledge gaps", "build a knowledge graph", "what's in my brain", or any question prefixed with "based on my past data" / "from my knowledge graph". Use for open-ended search, synthesis, and exploration over the user's Timeln m

Manages full-cycle Git operations including feature branch creation, conventional commit message generation, linear history synchronization (rebase), and push safety checks. Use this for git-related tasks.

Explorador de Repositórios GitHub. Ele analisa seu ambiente Claude Code + Codex App para recomendar automaticamente repositórios GitHub relevantes ou permite pesquisar no GitHub por palavras-chave. Responde a termos como "scout" e "repo search".

Use ao iniciar um novo projeto de código que precise de gerenciamento de tarefas estruturado, ciclo de vida RIPER-7, planejamento de versões, transferência de sessão e relatórios diários. Os gatilhos incluem "init workflow", "bootstrap .tasks", "initialize project workflow", "新项目初始化工作流", "初始化任务工作流".

Use when an output is at risk of verbosity — the TLDR-outside / details-inside discipline. Distinguished from chengyu-great-wisdom-looks-foolish on the representation axis — 大智若愚 = resist performative complexity, 言簡意賅 = resist sprawl. Orthogonal failure modes; you can be performatively-clever AND brief, or non-clever AND verbose.

Run a privacy impact assessment (PIA) for a product feature or initiative that collects, processes, or uses personal data. Use this skill when a new feature has privacy implications that need to be evaluated before launch.