security-bluebook-builder
FeaturedBuild a minimal but real security policy for sensitive apps. The output is a single, coherent Blue Book document using MUST/SHOULD/CAN language, with explicit assumptions, scope, and security gates.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- sickn33
- Repository
- sickn33/antigravity-awesome-skills
- Created
- 10 months ago
- Last Updated
- today
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
security-bluebook-builder
Build security Blue Books for sensitive apps
app-blueprint
This skill should be used when the user asks to "design a production architecture", "blueprint an app", "scaffold an architecture", "design a complete production-ready application", "architect this app", "give me a full system blueprint", "production architecture for X", or invokes /blueprint. Produces an 11-section senior-architect blueprint (folder tree, layers, data models, API contracts, deps, env, tests, CI/CD, notes, validation) from five required inputs (APP_DESCRIPTION, TECH_STACK, APP_TYPE, LANGUAGE, SCALE). Refuses to proceed if any input is missing. This is a greenfield architecture plan from an idea - it names a deployment target with rationale but does NOT emit infrastructure manifests (use docker-compose-architect or kubernetes-architect for those) and does NOT analyze or diagram an existing codebase (use codebase-to-mermaid / refactoring-analyst). Do NOT use for single-component design, code review, refactor planning, or throwaway prototypes.
security-page
Build a credible security/trust page for a developer tool before SOC 2 — concrete controls, encryption specifics, subprocessor list, responsible disclosure, data lifecycle, and honest scoping of what you can claim. Use when the user wants a security page, trust page, or trust center, asks "do we need SOC 2", got a vendor security questionnaire, or is losing deals to security review. Also use when they mention a DPA, subprocessors, security.txt, responsible disclosure, or "enterprise readiness", even if they never say "security page".