foryourhealth111-pixel/Vibe-Skills / bundled/skills/structured-content-storage
structured-content-storage
VerifiedEnforces structured, highly documented storage for code and data projects. Use when working on machine learning scripts, data processing, code creation, or script modification that should preserve clear structure and documentation.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.1 KB |
| assets/templates/CHANGELOG-template.md | markdown | 3.3 KB |
| assets/templates/DATA_DICTIONARY-template.md | markdown | 6.0 KB |
| assets/templates/PROCESS-template.md | markdown | 7.9 KB |
| assets/templates/data-processing-README.md | markdown | 3.5 KB |
| assets/templates/ml-project-README.md | markdown | 2.4 KB |
| references/comment-guidelines.md | markdown | 16.2 KB |
| references/directory-templates.md | markdown | 9.9 KB |
| references/documentation-standards.md | markdown | 6.9 KB |
| references/index.md | markdown | 1.3 KB |
references/index.md
View on GitHub# Structured Content Storage - References
Navigation guide for detailed documentation and standards.
## Core Documentation
### [documentation-standards.md](documentation-standards.md)
Comprehensive requirements for all documentation files including README, PROCESS, DATA_DICTIONARY, and CHANGELOG formats.
### [directory-templates.md](directory-templates.md)
Standard directory structures for different project types:
- Machine learning training projects
- Data processing and cleaning projects
- Analysis and research projects
- General software projects
### [comment-guidelines.md](comment-guidelines.md)
Best practices for code documentation:
- Function and class docstrings
- Inline comment standards
- File header requirements
- When and how to comment
## Quick Links
- **For new ML projects**: See directory-templates.md → ML Training Structure
- **For data cleaning**: See directory-templates.md → Data Processing Structure
- **For modifications**: See documentation-standards.md → CHANGELOG Requirements
- **For code comments**: See comment-guidelines.md → Function Documentation
## Usage
These references provide detailed specifications that supplement the Quick Reference in SKILL.md. Use them when you need:
- Detailed formatting requirements
- Edge case handling
- Extended examples
- Rationale for specific standards
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file). | Stars: 198k | Updated | Claude CodeCodex | Unverified | Install |
| doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |