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 |
assets/templates/CHANGELOG-template.md
View on GitHub# CHANGELOG Template
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
## [Unreleased]
### Added
- [List new features or files added]
### Changed
- [List modifications to existing functionality]
### Fixed
- [List bug fixes]
### Removed
- [List deprecated or removed features]
---
## [1.0.0] - YYYY-MM-DD
### Added
- Initial release
- [Feature 1]
- [Feature 2]
### Documentation
- Created README.md with project overview
- Created PROCESS.md with methodology
- Created DATA_DICTIONARY.md with field descriptions
---
## Template for New Entries
Copy this template when adding new changes:
```markdown
## [X.Y.Z] - YYYY-MM-DD
### Added
- New feature in `src/module.py:123-145`
- **What**: Description of new feature
- **Why**: Rationale for adding this feature
- **Usage**: How to use the new feature
### Changed
- Modified function in `src/module.py:67-89`
- **What**: Description of change
- **Why**: Rationale for change
- **Impact**: How this affects existing functionality
- **Breaking**: Yes/No - if yes, describe migration path
### Fixed
- Fixed bug in `src/module.py:234`
- **Issue**: Description of the bug
- **Cause**: Root cause analysis
- **Solution**: How it was fixed
- **Affected versions**: Which versions had this bug
### Removed
- Removed deprecated function `old_function()` from `src/module.py`
- **Reason**: Why it was removed
- **Replacement**: What to use instead
- **Migration**: How to update existing code
### Files Affected
- `src/module.py` (lines 67-89, 123-145, 234)
- `src/utils.py` (lines 45-52)
- `docs/PROCESS.md` (updated section 3)
- `README.md` (updated usage examples)
- `requirements.txt` (added new dependency: package-name==1.2.3)
```
---
## Version Numbering Guide
Use Semantic Versioning (MAJOR.MINOR.PATCH):
- **MAJOR** (X.0.0): Incompatible API changes or major restructuring
- **MINOR** (0.X.0): New features, backward-compatible
- **PATCH** (0.0.X): Bug fixes, backward-compatible
Examples:
- `1.0.0` → `1.0.1`: Bug fix
- `1.0.1` → `1.1.0`: New feature added
- `1.1.0` → `2.0.0`: Breaking change
---
## Change Categories
### Added
- New features
- New files or modules
- New configuration options
- New documentation
### Changed
- Modifications to existing features
- Performance improvements
- Refactoring (that affects behavior)
- Updated dependencies
### Fixed
- Bug fixes
- Security patches
- Corrected documentation
### Removed
- Deprecated features
- Removed files or modules
- Removed dependencies
### Security
- Security vulnerability fixes
- Security improvements
### Deprecated
- Features marked for removal in future versions
- Include timeline for removal
---
## Best Practices
1. **Update immediately**: Add entries as you make changes, not later
2. **Be specific**: Include file paths and line numbers
3. **Explain why**: Document rationale, not just what changed
4. **Link issues**: Reference issue numbers or tickets when applicable
5. **Date format**: Use ISO 8601 (YYYY-MM-DD)
6. **Keep chronological**: Most recent changes at the top
7. **Group related changes**: Combine related changes in one version entry
8. **Describe impact**: Explain how changes affect users or other code
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 |