mgiovani/ai-arsenal / skills/docs-init
docs-init
VerifiedBootstraps a documentation structure (architecture, onboarding, data-model, deployment, security, contributing, and a first ADR) for a project that has little or no docs/ directory, exploring the codebase and populating templates only with content evidenced in the code. Use when the user wants to set up docs, bootstrap documentation, initialize project docs, scaffold a docs/ folder, or create docs from scratch for a new or undocumented project. Not for refreshing or syncing docs that already exist (use docs-update). Not for generating a standalone architecture or ER diagram without the surrounding document (use docs-diagram).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.9 KB |
| assets/templates/architecture.md | markdown | 1.5 KB |
| assets/templates/contributing.md | markdown | 6.5 KB |
| assets/templates/data-model.md | markdown | 860 B |
| assets/templates/deployment.md | markdown | 1.2 KB |
| assets/templates/onboarding.md | markdown | 1.8 KB |
| assets/templates/security.md | markdown | 1.5 KB |
| evals/evals.json | config | 3.4 KB |
| evals/trigger-eval.json | config | 1.9 KB |
assets/templates/security.md
View on GitHub# {{PROJECT_NAME}} - Security
**Last Updated:** {{DATE}}
## Overview
This document outlines data security policies, access controls, and encryption
strategies for {{PROJECT_NAME}}, based on what the codebase actually implements.
## Data Classification
<!-- One row per data category the codebase evidences (user PII table, payment
fields, internal logs, etc). Delete rows with no evidence. -->
| Category | Description | Access Control |
|----------|--------------|-----------------|
| {{DATA_CATEGORY}} | {{CATEGORY_DESCRIPTION}} | {{CATEGORY_ACCESS}} |
## Authentication and Authorization
{{AUTH_STRATEGY}}
[The real mechanism found in code: session cookies, JWT, OAuth provider, RBAC
middleware, etc.]
## Encryption
**Data at rest:** {{ENCRYPTION_AT_REST}}
**Data in transit:** {{ENCRYPTION_IN_TRANSIT}}
## Compliance
<!-- Only include a regulation if the codebase shows real evidence of it
(GDPR consent flows, HIPAA PHI handling, a documented DPA, etc).
Delete this entire section if no compliance work is evidenced. -->
{{COMPLIANCE_REQUIREMENTS}}
## Incident Response
{{INCIDENT_RESPONSE}}
[Link to a runbook if one exists; otherwise note that none exists yet.]
## Security Testing
{{SECURITY_TESTING}}
[Only what's evidenced: a dependabot/CI security scan step, a SAST tool config.
Omit speculative pentest schedules.]
## References
- [Data Model Documentation](data-model.md)
- [Architecture Overview](architecture.md)
---
*This document may contain sensitive security information. Restrict access appropriately.*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |