Skip to content
Back to skills

924 Location Of Feature Documentationinstructions 15e08d43

ASecurity

All new feature documentation should be placed in: ``` ..\docs\explanation\features\ ```

  • 9 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 11, 2026
documentationtestingapiperformancedocumentation

Works with

  • api

Security analysis

A100/100

Scanned October 11, 2026

npx -y skills add tools-only/X-Skills --skill 924-location_of_feature_documentationinstructions_15e08d43 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of 924 Location Of Feature Documentationinstructions 15e08d43?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for 924 Location Of Feature Documentationinstructions 15e08d43
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tools-only-924-location-of-feature-documentationinstructions/badge)](https://www.skillsdirectory.com/skills/tools-only-924-location-of-feature-documentationinstructions)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

SKILL.md
---
applyTo: '**'
---

# Feature Documentation Location

## Documentation Directory
All new feature documentation should be placed in:
```
..\docs\explanation\features\
```

## File Naming Convention
Use descriptive, uppercase names with underscores:
- `[FEATURE_NAME].md`
- Example: `AGENT_ORCHESTRATION.md`
- Example: `FILE_UPLOAD_SYSTEM.md`

## Required Documentation Structure
Each feature documentation file must include:

### 1. Header Information
- Feature title
- Overview and purpose
- Version implemented
- Dependencies

### 2. Technical Specifications
- Architecture overview
- API endpoints (if applicable)
- Configuration options
- File structure

### 3. Usage Instructions
- How to enable/configure
- User workflows
- Examples and screenshots
- Integration points

### 4. Testing and Validation
- Test coverage
- Performance considerations
- Known limitations

## Integration Process
When documenting a new feature:
1. Create markdown file in `..\docs\features\`
2. Include current config.py version
3. Reference related functional tests
4. Link to any fix documentation if the feature required bug fixes

## Cross-References
Feature documentation may reference:
- Related fix documentation in `..\docs\fixes\`
- Functional test files in `functional_tests\`
- Configuration changes in `config.py`
- Other features in `..\docs\features\`

## Maintenance
Keep feature documentation updated when:
- Feature capabilities are enhanced
- Configuration options change
- Integration methods are modified
- Related fixes impact feature behavior

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.