메뉴
Learned from user correction: Correction: Avoid: 'map clearly to any specific sdlc phase: - `normalize-structure-after-exploration' | Expected behavior: 'be tagged with which sdlc phases based on my review of all 73 files (notes 293-365)'
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Detect AI writing patterns in text. Use when: (1) need to check if text sounds AI-generated, (2) reviewing content before publication, (3) analyzing writing for Wikipedia-style AI markers, (4) generating report-only analysis without changes.
Use when: (1) User asks to "review for AI writing" or "check for LLM signs" (2) User wants to "detect AI-generated text" or "humanize this document" (3) User wants to identify and fix signs of AI/LLM-generated writing (4) User mentions Wikipedia AI writing guidelines
Fix AI writing patterns in text. Use when: (1) ai-writing-analyzer found issues to fix, (2) need to humanize AI-generated content, (3) preparing content for publication, (4) iteratively refining text until clean.
Humanize a document by removing AI-writing patterns via a multi-agent workflow (analyze → revise → adversarial review → loop-until-clean). Use when the user asks to "humanize", "de-AI", "remove AI tells", or "review for AI writing" on a file.
Fix for Claude Code slash command frontmatter that fails to parse when `argument-hint:` is given square-bracketed placeholder values. Use when: (1) authoring `commands/<name>.md` files in a CC plugin and the frontmatter shows `argument-hint: [working-dir] [team-name]` or similar multi-token bracketed values; (2) a frontmatter-validation test (e.g. `yaml.safe_load(block)` over the SKILL/command frontmatter) raises `ScannerError` or `ConstructorError` complaining about flow sequences or "expected a mapping"; (3) the slash command silently doesn't appear in `/help` after install, or a plugin-marketplace test asserting the `description` field is present trips because the whole frontmatter parse blew up. The fix is to QUOTE the value as a single string. Covers the same trap for `commands/<name>.md` directly authored in CC format AND APM-managed marketplaces shipping commands via APM.
Organize GitHub repository issues with proper milestones, native relationships, and clean labeling structure. Use when grooming issues, setting up milestones, establishing dependencies, or cleaning up issue tracking in a GitHub repository.
| name | correction-avoid-map-clearl |
| description | Learned from user correction: Correction: Avoid: 'map clearly to any specific sdlc phase: - `normalize-structure-after-exploration' | Expected behavior: 'be tagged with which sdlc phases based on my review of all 73 files (notes 293-365)' |
| author | Claude Code (extracted by Claudeception v4.0) |
| version | 1.0.0 |
| date | "2026-01-30T00:00:00.000Z" |
| tags | ["correction","learned","negation_reference"] |
| level | user |
| breakthrough_score | 4.12 |
When making similar mistakes to: negation_reference
Correction: Avoid: 'map clearly to any specific sdlc phase: - `normalize-structure-after-exploration' | Expected behavior: 'be tagged with which sdlc phases based on my review of all 73 files (notes 293-365)'
