Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

cli-forge-arch

Estrelas5

Forks1

Atualizado8 de junho de 2026 às 14:55

Router for architecture design. Detects whether the user needs an HLD or LLD and delegates to the appropriate skill. Use when the user says 'design doc', 'architecture', or is ambiguous about HLD vs LLD. For explicit HLD requests, use cli-forge-hld directly. For explicit LLD requests, use cli-forge-lld directly.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

Destynova2

Destynova2/cli-code-skills

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

Explorador de arquivos

4 arquivos

SKILL.md

readonly

name	cli-forge-arch
metadata	{"author":"clement"}
description	Router for architecture design. Detects whether the user needs an HLD or LLD and delegates to the appropriate skill. Use when the user says 'design doc', 'architecture', or is ambiguous about HLD vs LLD. For explicit HLD requests, use cli-forge-hld directly. For explicit LLD requests, use cli-forge-lld directly.
argument-hint	[system-name-or-description]
context	fork
agent	general-purpose

Language rule: Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the document in that language. If the project is bilingual, ask the user which language to use before proceeding.

Gotchas — read ../gotchas.md before producing output to avoid known mistakes.

Arch Router — HLD / LLD Dispatcher

This skill has been split into two focused skills. Route the user's request accordingly:

Routing Table

Signal in user's request	Delegate to
"HLD", "system design", "architecture", "C4 context/container", "capacity", "back-of-envelope", "ATAM", "Gate review", "design proposal"	`/cli-forge-hld`
"LLD", "detailed design", "class diagram", "sequence diagram", "API spec", "DB schema", "component design", "STRIDE", "threat model"	`/cli-forge-lld`
"design doc", "tech spec" (ambiguous)	Ask the user: "Do you want a high-level design (system architecture, C4 L1-L2, capacity estimation, ADRs) or a low-level design (class diagrams, API contracts, DB schemas, sequence diagrams)?"
Both mentioned	Produce HLD first, then LLD for each key container

What changed

The original cli-forge-arch combined HLD and LLD in a single skill. This caused issues:

Users asking for HLD got LLD-level detail (class diagrams, DB schemas) they didn't need
Users asking for LLD got HLD-level context (system diagrams, capacity) that was redundant
The skill was too large to produce focused, high-quality output

New skills:

cli-forge-hld — C4 L1-L2, capacity estimation, ADRs, ATAM tradeoff analysis, deployment architecture
cli-forge-lld — C4 L3-L4, class/sequence/state diagrams, API contracts, DB schemas, STRIDE, testability

The references/ directory is preserved here for backward compatibility but the canonical references now live in each skill's own references/ directory.

Mais deste repositório

mesmo repositório

cli-audit-doc

Destynova2/cli-code-skills

Audit documentation quality with weighted scoring across 12 dimensions (Diataxis coverage, completeness, freshness, readability, examples, accessibility, CI testing). Detects doc anti-patterns (Wall of Text, The Lie, Jargon Soup). Use when reviewing doc quality, auditing documentation, checking for stale docs, or saying 'audit docs', 'doc quality', 'documentation review'. Invoke with an optional file or directory path.

2026-07-155

cli-forge-doc

Destynova2/cli-code-skills

Generate and audit comprehensive project documentation from a Git repository. Produces standard documentation (CONTRIBUTING.md, architecture, troubleshooting) in Diataxis structure with zero AI markers by default. Use this skill whenever someone asks to document a project, generate docs, create a README, write API docs, or improve existing documentation. Also trigger when someone mentions "doc", "documentation", "readme", "explain this codebase", "onboard developers", or "make this project understandable".

2026-07-155

cli-forge-plume

Destynova2/cli-code-skills

Ghostwrite, rewrite, and audit everyday professional exchanges in the user's voice: emails, replies, chat messages (Slack/Teams/Discord), LinkedIn DMs, client and recruiter answers, follow-ups, thank-yous, refusals, bad-news notes, meeting requests, and short announcements. Enforces zero AI tells (no em-dash reflex, no AI vocabulary, no assistant structure), front-loaded asks, one message = one ask, target-language proofreading with correct diacritics, and calibrated light humor for follow-ups. USE BY DEFAULT — even without a trigger word — whenever creating, editing, rewriting, translating, or auditing ANY text the user will send or publish in their name: message, mail, réponse, annonce, petite annonce, post, commentaire, DM, description produit, texte de formulaire. If the task involves producing or modifying user-facing prose, load this skill first. Also triggers on 'écris un mail', 'réponds à', 'relance', 'relance-le', 'follow up', 'reformule ce message', 'humanize this', 'sounds like AI', 'trop formel',

2026-07-155

cli-forge-resilience

Destynova2/cli-code-skills

Generate a production-parity resilience blueprint: test battery, troubleshooting runbook, agent-ready operations pack, failure-injection plan, and incident blackbox templates. Uses biological and physical reasoning — genome/contracts, membranes/boundary conditions, homeostasis/health checks, immune system/negative tests, stress-strain/failure budgets, phase transitions/resource cliffs, hysteresis/reruns, and memory cells/post-incident capitalisation. Use whenever the user asks to prevent prod bugs, make dev/staging closer to prod, design pre-prod checks, write a runbook, create a smoke test ladder, harden deployments, define N1/N2/N3 operations, govern agent autonomy, or turn incidents into durable anti-regressions.

2026-07-155

cli-audit-hanoi

Destynova2/cli-code-skills

Audit the ordering and layering of install/config/build steps using the Tower of Hanoi model: stable-and-expensive at the bottom, volatile-and-cheap on top, no step before its prerequisite, minimal redone work per change, and no responsibility displaced to a higher layer (what the code does not do resurfaces in Docker, kube.yml, or Ansible — often paid three times). Applies to Dockerfiles/Containerfiles (layer cache, image size), Ansible playbooks/roles (task order, handler restarts, idempotence), Kubernetes manifests (apply order, CRD/RBAC/ConfigMap sequencing), Rust workspaces and build systems (crate layering, incremental compile blast radius), CI job ordering, long documents (reader-cache ordering), and cross-layer stacks (code -> image -> orchestrator -> config management). Use when the user says 'hanoi', 'Tours de Hanoï', 'ordre d'installation', 'ordre des tâches', 'layer order', 'layer caching', 'Dockerfile cache', 'ça rebuild tout', 'build lent', 'image trop grosse', 'restart storm', 'apply order', 's

2026-07-045

cli-audit-shell

Destynova2/cli-code-skills

Audit shell scripts against Google Shell Style Guide + ops best practices. Scores 12 dimensions: strict mode coherence, error surfaces, logging, stderr hygiene, variable discipline, quoting, control flow, naming, CLI ergonomics, idempotency, namespace, and security. Goes beyond shellcheck — detects semantic anti-patterns invisible to linters (dead fallbacks under set -e, custom loggers vs logger(1), redundant package checks, env var injection in heredocs, missing getopts). Use when reviewing shell scripts, auditing bash code, checking deployment scripts, or saying 'audit shell', 'bash review', 'script quality', 'shell style', 'shellcheck not enough', 'review my script'. Also triggers on 'set -euo pipefail', 'getopts', 'shell injection', 'logger', 'bash best practices', 'google shell style'.

2026-07-045

name	cli-forge-arch
metadata	{"author":"clement"}
description	Router for architecture design. Detects whether the user needs an HLD or LLD and delegates to the appropriate skill. Use when the user says 'design doc', 'architecture', or is ambiguous about HLD vs LLD. For explicit HLD requests, use cli-forge-hld directly. For explicit LLD requests, use cli-forge-lld directly.
argument-hint	[system-name-or-description]
context	fork
agent	general-purpose

Language rule: Skill instructions are written in English. When generating user-facing output, detect the project's primary language (from README, comments, docs, commit messages) and produce the document in that language. If the project is bilingual, ask the user which language to use before proceeding.

Gotchas — read ../gotchas.md before producing output to avoid known mistakes.

Arch Router — HLD / LLD Dispatcher

This skill has been split into two focused skills. Route the user's request accordingly:

Routing Table

Signal in user's request	Delegate to
"HLD", "system design", "architecture", "C4 context/container", "capacity", "back-of-envelope", "ATAM", "Gate review", "design proposal"	`/cli-forge-hld`
"LLD", "detailed design", "class diagram", "sequence diagram", "API spec", "DB schema", "component design", "STRIDE", "threat model"	`/cli-forge-lld`
"design doc", "tech spec" (ambiguous)	Ask the user: "Do you want a high-level design (system architecture, C4 L1-L2, capacity estimation, ADRs) or a low-level design (class diagrams, API contracts, DB schemas, sequence diagrams)?"
Both mentioned	Produce HLD first, then LLD for each key container

What changed

The original cli-forge-arch combined HLD and LLD in a single skill. This caused issues:

Users asking for HLD got LLD-level detail (class diagrams, DB schemas) they didn't need
Users asking for LLD got HLD-level context (system diagrams, capacity) that was redundant
The skill was too large to produce focused, high-quality output

New skills:

cli-forge-hld — C4 L1-L2, capacity estimation, ADRs, ATAM tradeoff analysis, deployment architecture
cli-forge-lld — C4 L3-L4, class/sequence/state diagrams, API contracts, DB schemas, STRIDE, testability

The references/ directory is preserved here for backward compatibility but the canonical references now live in each skill's own references/ directory.