This skill should be used when the user asks about "update documentation", "CLAUDE.md", "README.md", "documentation conventions", "document this", "add to docs", "update the readme", or discusses project documentation maintenance and standards.
Maintains project documentation standards for CLAUDE.md, README.md, and technical docs. Triggered when users request documentation updates, discuss docs, or ask to "document this" or "update the readme".
/plugin marketplace add jwmyers/vui-vux-plugins/plugin install zero-day-dev@vui-vuxThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Expert knowledge of Zero-Day Attack documentation conventions, structure, and maintenance for CLAUDE.md, README.md, and project documentation.
Primary guidance file for Claude Code:
| Section | Purpose |
|---|---|
| Project Overview | What the project is |
| Build Commands | How to build/deploy |
| Required Build Configuration | Platform settings |
| Architecture | Code organization |
| Key Namespaces | Namespace purposes |
| Singleton Managers | Global access patterns |
| Board SDK Components | SDK overview |
| Project Structure | File organization |
| SVG Import Settings | Sprite sizing rules |
| Visual Style Guide | Colors summary |
| Layout Configuration | Layout constants |
| Testing | Test instructions |
| Unity MCP Integration | MCP setup/usage |
User-facing project introduction:
| Section | Purpose |
|---|---|
| Game Overview | What the game is |
| Digitization Approach | Hybrid input model |
| Tech Stack | Engine, platform, SDK |
| Getting Started | Setup instructions |
| Building & Deploying | Build commands |
| Simulation | Testing without hardware |
| Project Structure | Directory overview |
| Documentation | Doc file index |
| AI-Assisted Development | MCP quick start |
| Credits | Attribution |
Detailed technical documentation:
| File | Content |
|---|---|
ARCHITECTURE-ANALYSIS.md | Code architecture details |
DIGITIZATION-ANALYSIS.md | Implementation specs |
RULES-ANALYSIS.md | Game mechanics breakdown |
BOARD-TILE-SIZING-ANALYSIS.md | Layout and sizing guide |
game-visual-style-guide.md | Colors and styling |
Unity-MCP-Documentation.md | MCP setup and usage |
ZERO-DAY-ATTACK-rules-instructions.md | Official rulebook |
Board-SDK-Documentation/ | SDK reference manual |
Use consistent formatting:
# for title, ## for sections, ### for subsections- for unordered, 1. for orderedAlways include language identifier:
```csharp
public class Example { }
```
```bash
bdb install app.apk
```
Use for structured data:
| Column 1 | Column 2 |
| -------- | -------- |
| Value 1 | Value 2 |
Use relative paths from project root:
See `Documentation/ARCHITECTURE-ANALYSIS.md`
Located in `Assets/Scripts/Config/`
Update CLAUDE.md when:
Script Organization: Update when adding folders/namespaces
Assets/Scripts/
├── NewFolder/ # Purpose
│ └── NewClass.cs # Description
Key Namespaces: Update when adding namespaces
| `ZeroDayAttack.NewNamespace` | Purpose |
Singleton Managers: Update when adding managers
- `NewManager.Instance` - Description
Update README.md when:
README is for users, not AI:
Update Documentation files when:
Use UPPERCASE-WITH-DASHES for analysis docs:
NEW-FEATURE-ANALYSIS.md
SYSTEM-NAME-DOCUMENTATION.md
Update skill SKILL.md files when:
Update agent .md files when:
Update command .md files when:
# Feature Name Analysis
## Overview
Brief description of the feature.
## Implementation
### Architecture
How it fits in the codebase.
### Key Classes
| Class | Purpose |
| --------- | ----------- |
| ClassName | Description |
### Data Flow
How data moves through the system.
## Usage
How to use the feature.
## Testing
How to test the feature.
## ClassName
Brief description.
### Properties
| Property | Type | Description |
| -------- | ---- | ------------ |
| Name | Type | What it does |
### Methods
#### MethodName
```csharp
public ReturnType MethodName(ParamType param)
```
Description of method.
**Parameters:**
- `param`: Description
**Returns:** Description
After significant changes:
Ensure consistency between:
Study existing documentation:
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.