com um clique
sentinel-protocol
sentinel-protocol contém 8 skills coletadas de stnl-studios, com cobertura ocupacional por repositório e páginas de detalhe dentro do site.
Skills neste repositório
Stack-neutral backend quality guardrail for implementation and review, focused on preserving project architecture, responsibilities, persistence patterns, contracts, transaction boundaries, testability, and basic backend safety.
Backend data persistence quality guardrail for implementation and review, focused on SQL, ORM, NoSQL, cache, migrations, transactions, indexes, query safety, bounded access, and consistency.
Stack-neutral frontend quality guardrail for implementation and review, focused on preserving UI boundaries, service/facade/store usage, component responsibility, form flows, mapping, async lifecycle safety, design system reuse, UI states, contract safety, performance, and testability.
Portable iOS Swift quality guardrail for implementation and review, focused on SwiftUI and UIKit boundaries, state ownership, concurrency safety, lifecycle cleanup, navigation, forms, networking, persistence, design system reuse, platform conventions, and testability.
Descobre, materializa, revisa, atualiza e remove o conjunto minimo util de agents especializados de um repo alvo ja preparado por stnl_project_context ou, em greenfield, por stnl_project_foundation.
Levanta contexto factual do projeto e materializa ou ressincroniza docs em docs/core, docs/units e docs/features com modos BOOTSTRAP, RESYNC e TBD_SYNC.
Estrutura a fundacao documental Sentinel de projetos greenfield, inception ou repos novos a partir de documentacao bruta, decisoes explicitas e contratos declarados, priorizando docs/features e preparando handoff futuro para stnl_project_context sem inventar fatos de codebase.
Amadurece uma ideia, bug, pedido ou recorte parcial em uma SPEC confiavel, rastreavel e consumivel por outros agentes, sem conduzir o fluxo. Use quando for preciso consolidar problema, objetivo, escopo, fluxos, criterios de aceite, riscos e decisoes legitimas sem inventar requisitos, preservando `feature_spec.md` como artefato canônico principal dentro de um bundle canônico obrigatório, com retomada explicita via `MODE=RESUME`, enriquecimento de Planning Interface via `MODE=PLANNING_INTERFACE` e fechamento limitado ao artefato da SPEC, nunca ao workflow.