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/PROCESS-template.md
View on GitHub# PROCESS Documentation Template
Comprehensive documentation of the workflow, methodology, and key decisions.
## Overview
**Project**: [Project Name]
**Purpose**: [Brief description of what this process accomplishes]
**Input**: [Description of input data/requirements]
**Output**: [Description of output/deliverables]
**Duration**: [Typical execution time]
---
## Workflow Diagram
```
[Input Data] → [Step 1] → [Step 2] → [Step 3] → [Output]
↓ ↓ ↓
[Validation] [Transform] [Quality Check]
```
---
## Detailed Process Steps
### Step 1: [Step Name]
**Purpose**: [What this step accomplishes]
**Input**:
- [Input 1]: Description
- [Input 2]: Description
**Process**:
1. [Sub-step 1]: Detailed description
2. [Sub-step 2]: Detailed description
3. [Sub-step 3]: Detailed description
**Output**:
- [Output 1]: Description
- [Output 2]: Description
**Validation**:
- [Check 1]: What is validated and how
- [Check 2]: What is validated and how
**Error Handling**:
- [Error type 1]: How it's handled
- [Error type 2]: How it's handled
**Example**:
```python
# Code example showing this step
result = process_step_1(input_data)
```
**Performance**:
- Time complexity: O(n)
- Space complexity: O(n)
- Typical duration: [X seconds/minutes]
---
### Step 2: [Step Name]
**Purpose**: [What this step accomplishes]
**Input**:
- [Input from previous step]
**Process**:
1. [Sub-step 1]: Detailed description
- Rationale: [Why this approach]
- Alternative considered: [Other approaches and why rejected]
2. [Sub-step 2]: Detailed description
3. [Sub-step 3]: Detailed description
**Output**:
- [Output description]
**Key Parameters**:
- `parameter_1`: Description and default value
- `parameter_2`: Description and default value
**Validation**:
- [Validation checks performed]
**Example**:
```python
# Code example
result = process_step_2(previous_result, param1=value1)
```
---
### Step 3: [Step Name]
**Purpose**: [What this step accomplishes]
**Input**:
- [Input from previous step]
**Process**:
1. [Sub-step 1]
2. [Sub-step 2]
3. [Sub-step 3]
**Output**:
- [Final output description]
**Quality Checks**:
- [Check 1]: Acceptance criteria
- [Check 2]: Acceptance criteria
**Example**:
```python
# Code example
final_result = process_step_3(previous_result)
```
---
## Key Decisions and Rationale
### Decision 1: [Decision Title]
**Context**: [What situation required this decision]
**Options Considered**:
1. **Option A**: [Description]
- Pros: [Advantages]
- Cons: [Disadvantages]
2. **Option B**: [Description]
- Pros: [Advantages]
- Cons: [Disadvantages]
3. **Option C**: [Description]
- Pros: [Advantages]
- Cons: [Disadvantages]
**Decision**: [Which option was chosen]
**Rationale**: [Why this option was selected]
**Trade-offs**: [What was sacrificed for what benefit]
**Impact**: [How this affects the overall process]
---
### Decision 2: [Decision Title]
**Context**: [Situation]
**Decision**: [What was decided]
**Rationale**: [Why]
**Alternatives**: [What else was considered]
---
## Data Flow
### Input Data Flow
```
Source System → Raw Data Storage → Validation → Processing Pipeline
↓ ↓ ↓ ↓
[Details] [Location] [Checks] [Steps]
```
### Processing Data Flow
```
Raw Data → Cleaning → Transformation → Feature Engineering → Output
↓ ↓ ↓ ↓ ↓
[Format] [Rules] [Methods] [Features] [Format]
```
### Output Data Flow
```
Processed Data → Quality Check → Storage → Downstream Systems
↓ ↓ ↓ ↓
[Format] [Criteria] [Location] [Usage]
```
---
## Configuration
### Required Configuration
**File**: `configs/config.yaml`
```yaml
# Input configuration
input:
path: "data/raw/"
format: "csv"
encoding: "utf-8"
# Processing configuration
processing:
batch_size: 1000
parallel: true
num_workers: 4
# Output configuration
output:
path: "data/processed/"
format: "csv"
compression: "gzip"
# Quality thresholds
quality:
min_completeness: 0.95
max_outlier_ratio: 0.05
```
### Optional Configuration
[List optional parameters and their defaults]
---
## Dependencies
### System Requirements
- Python >= 3.8
- Memory: >= 8GB RAM
- Disk space: >= 10GB free
### Software Dependencies
- pandas >= 1.3.0
- numpy >= 1.20.0
- scikit-learn >= 0.24.0
See `requirements.txt` for complete list.
---
## Performance Characteristics
### Scalability
- **Small datasets** (<10K records): ~1 second
- **Medium datasets** (10K-1M records): ~1 minute
- **Large datasets** (>1M records): ~10 minutes
### Bottlenecks
1. [Bottleneck 1]: Description and mitigation
2. [Bottleneck 2]: Description and mitigation
### Optimization Opportunities
1. [Opportunity 1]: Potential improvement
2. [Opportunity 2]: Potential improvement
---
## Error Handling
### Common Errors
**Error 1: [Error Name]**
- **Cause**: [What causes this error]
- **Symptoms**: [How to recognize it]
- **Solution**: [How to fix it]
- **Prevention**: [How to avoid it]
**Error 2: [Error Name]**
- **Cause**: [What causes this error]
- **Symptoms**: [How to recognize it]
- **Solution**: [How to fix it]
- **Prevention**: [How to avoid it]
### Error Recovery
- [Description of automatic recovery mechanisms]
- [Manual intervention procedures]
---
## Quality Assurance
### Validation Checks
1. **Input Validation**
- Schema validation
- Data type checks
- Range validation
- Completeness checks
2. **Process Validation**
- Intermediate result checks
- Consistency validation
- Logic verification
3. **Output Validation**
- Quality metrics
- Completeness verification
- Format validation
- Business rule checks
### Quality Metrics
| Metric | Target | Actual | Status |
|--------|--------|--------|--------|
| Completeness | ≥95% | [X%] | [Pass/Fail] |
| Validity | ≥99% | [X%] | [Pass/Fail] |
| Accuracy | ≥98% | [X%] | [Pass/Fail] |
| Timeliness | <1 hour | [X min] | [Pass/Fail] |
---
## Monitoring and Logging
### Logging Strategy
- **Level**: INFO for normal operations, DEBUG for troubleshooting
- **Location**: `logs/process_YYYYMMDD.log`
- **Retention**: 30 days
### Key Metrics Logged
1. Processing duration
2. Record counts (input/output)
3. Error counts by type
4. Quality metrics
5. Resource usage (memory, CPU)
### Monitoring Alerts
- [Alert 1]: Condition and action
- [Alert 2]: Condition and action
---
## Testing
### Test Strategy
1. **Unit tests**: Test individual functions
2. **Integration tests**: Test complete workflow
3. **Data validation tests**: Test data quality
4. **Performance tests**: Test scalability
### Test Data
- **Location**: `tests/data/`
- **Description**: [Description of test datasets]
### Running Tests
```bash
# Run all tests
pytest tests/
# Run specific test
pytest tests/test_process.py::test_step_1
```
---
## Maintenance
### Regular Maintenance Tasks
1. [Task 1]: Frequency and procedure
2. [Task 2]: Frequency and procedure
### Update Procedures
1. [How to update configuration]
2. [How to update code]
3. [How to update documentation]
---
## Troubleshooting
### Issue 1: [Issue Description]
**Symptoms**: [How to recognize]
**Diagnosis**: [How to diagnose]
**Solution**: [How to fix]
### Issue 2: [Issue Description]
**Symptoms**: [How to recognize]
**Diagnosis**: [How to diagnose]
**Solution**: [How to fix]
---
## References
### Internal Documentation
- [Link to related documentation]
- [Link to API documentation]
### External Resources
- [Link to relevant papers/articles]
- [Link to library documentation]
---
## Change History
### 2026-01-19
- Updated Step 2 to include new validation checks
- Added performance optimization in Step 3
- Updated quality metrics thresholds
### 2026-01-15
- Initial process documentation created
---
## Contact
**Process Owner**: [Name]
**Email**: [Email]
**Last Updated**: [Date]
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 |