bac2b27bb8
BREAKING CHANGES: - Remove -cskill suffix from all skill names (use standard kebab-case) - Simplify marketplace.json to only official fields (fixes Issue #5) - SKILL.md body must be <500 lines (progressive disclosure via references/) New features: - Cross-platform support for 8+ platforms (Claude Code, Copilot, Cursor, Windsurf, Cline, Codex CLI, Gemini CLI) - scripts/install-template.sh: Auto-detect platform installer with --dry-run - scripts/validate.py: Spec compliance checker for generated skills - scripts/security_scan.py: Security scanner for hardcoded keys and dangerous patterns - MIGRATION.md: v3.x to v4.0 migration guide - 6 new reference files for progressive disclosure from lean SKILL.md Key changes: - SKILL.md: 4,116 → 272 lines with spec-compliant YAML frontmatter - marketplace.json: Stripped to {name, plugins} only - article-to-prototype-cskill/ → article-to-prototype/ - stock-analyzer-cskill/ → stock-analyzer/ - Export system integrates validation + security scanning - README.md rewritten for all supported platforms - Phase 5 pipeline outputs SKILL.md-first, spec-compliant skills Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
28 lines
1,014 B
Markdown
28 lines
1,014 B
Markdown
# SC-042: Uppercase Name Auto-Converts to Lowercase Kebab-Case
|
|
|
|
> Covers: FR-001, Edge case 2.3 — Name contains uppercase or special chars: auto-convert to lowercase kebab-case
|
|
> Type: Edge Case
|
|
|
|
## Given
|
|
- The meta-skill is processing a skill where the derived name would be "MyAwesome_DataProcessor"
|
|
|
|
## When
|
|
- The name normalization step runs
|
|
|
|
## Then
|
|
- The name is auto-converted to `my-awesome-data-processor` (lowercase kebab-case)
|
|
- Underscores are replaced with hyphens
|
|
- Uppercase letters are lowered
|
|
- The user is informed of the conversion
|
|
|
|
## Verification Method
|
|
|
|
**Method**: Automated test
|
|
|
|
**Steps**:
|
|
1. Generate a skill where the initial name would contain uppercase/special chars
|
|
2. Parse the final SKILL.md frontmatter `name` field
|
|
3. Assert `name` matches regex `^[a-z][a-z0-9-]*[a-z0-9]$`
|
|
4. Assert no uppercase letters, underscores, or special chars remain
|
|
|
|
**Expected evidence**: `name: my-awesome-data-processor`. All lowercase. Hyphens as separators. No underscores or special characters.
|