format-standardizelisted

# Format & Standardize Skill ## Purpose Ensures the generated deliverable follows consistent formatting, style, and structure standards. This is the "polish" step that makes work look professional and maintainable. ## What to Do 1. **Review the generated deliverable** 2. **Load their standards** to understand formatting preferences 3. **Apply standardization**: - Code formatting (indentation, naming, structure) - Documentation formatting (headers, lists, spacing) - Consistency across all elements - Professional appearance 4. **Use their tools/conventions** if specified: - Example: "Use Prettier for code" - Example: "Use Markdown standard headers" 5. **Verify complete consistency** before delivery ## Format Checks by Type ### Code Features - [ ] Consistent indentation (spaces/tabs) - [ ] Naming conventions (camelCase, snake_case, etc.) - [ ] Consistent spacing around operators and braces - [ ] Comments formatted consistently - [ ] Imports/exports organized - [ ] Line length consistent - [ ] Semicolons or no-semicolons applied consistently - [ ] Quotes style (single/double) consistent ### Documentation - [ ] Consistent header levels (# ## ###) - [ ] Consistent list formatting (bullets vs numbers) - [ ] Code blocks properly formatted - [ ] Links properly formatted - [ ] Consistent spacing between sections - [ ] Table formatting (if applicable) - [ ] Consistent punctuation ### Refactoring - [ ] Before code formatted consistently - [ ] After code formatte