원클릭으로
context-formatting-linting
Specialized rules for repairing Markdown lint errors in Gold Context files (MD025, MD060, MD024).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Specialized rules for repairing Markdown lint errors in Gold Context files (MD025, MD060, MD024).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
Use this skill when designing, creating, or modifying API endpoints; defining contracts between services; evaluating protocol choices (REST, GraphQL, gRPC, WebSockets); versioning or deprecating an API; designing error responses or pagination; or reviewing an existing API for consistency, security, or ergonomics. Signal phrases: "design the API", "create an endpoint", "REST", "GraphQL", "gRPC", "API versioning", "backward compatible", "breaking change", "error response", "pagination", "rate limiting", "API contract", "OpenAPI", "Protobuf", "webhook", "idempotency", "deprecation", "endpoint structure". Also activate when API responses expose database column names, collection endpoints return unbounded results, or breaking changes are being introduced to active versions without a migration plan. Do NOT shape the API contract around implementation convenience — design for the consumer and the future.
Use this skill when designing system boundaries, data flows, component interfaces, or making structural technology decisions. Activated when the user is initializing a new project, service, or major feature; designing data flow between components; breaking apart a legacy system; defining folder structures or project organization; evaluating core technology or framework choices; or when the current system fails to scale. Examples: "how should I structure this?", "should this be a microservice?", "design the architecture for X", "what's the best way to organize this codebase?", "how should data flow between these components?". Do NOT use for pure implementation (use coding skill) or infrastructure provisioning (use devops-infra skill).
Use this skill when analyzing a brand's positioning, auditing an existing website's brand communication, identifying mismatches between brand intent and visual/copy execution, or defining the brand strategy for a new business from scratch. Activated when the user asks to "audit the brand", "diagnose the brand's positioning", "align copy and visuals to the brand", "define the brand perception", "what phase is this brand in", or "how does the brand extend to visuals and animations". Do NOT use for writing actual copy (use copywriting), editing copy (use copy-editing), or configuring animations without brand direction (use cinematic-motion).
Use this skill when designing or implementing highly animated, immersive, and cinematic web user interfaces. Activated when the user asks to build animations, integrate GSAP, use ScrollTrigger, build Three.js R3F models, implement video-scrubbing, image mask scaling, modulo-based infinite sliders, bento grid lighting, or premium interactive web layouts. Do NOT use for standard, non-animated web interfaces or pure backend APIs.
Use this skill when building cinematic, animated, or immersive web experiences. Covers scroll-driven storytelling (GSAP, ScrollTrigger, SplitText, video scrubbing, parallax, mask reveals), 3D product showcases (R3F, Zustand, studio lighting, model switching, video textures), layout composition (bento grids, masonry, power lines, overlapping typography), and register-aware creative direction. Activated when the user asks to "build a cinematic landing page", "add scroll animations", "create a 3D product viewer", "scrub video on scroll", "build a bento grid with scroll reveals", "animate text on scroll", "add parallax effects", "create a mask reveal", "build an infinite slider", "implement model switching", "add studio lighting to 3D scene", "map video textures on 3D screens", or any task producing premium animated web surfaces. Also activated for FFmpeg keyframe encoding, GSAP ScrollTrigger configuration, SplitText typography, gltfjsx model conversion, Zustand state for 3D, or scroll-bound timeline orchestratio
Use this skill when writing, modifying, or generating code of any kind. Activated when the user asks to build features, implement functions, create components, write endpoints, set up forms, wire things together, or produce any working implementation. Trigger phrases: "build this", "implement", "write the code for", "create a function that", "add this endpoint", "make it work", "update this code to", "wire this together". Do NOT use for: pure architectural decisions before implementation starts (use architecture skill), root-cause debugging of existing broken code (use debugging skill).
SOC 직업 분류 기준
| name | CONTEXT FORMATTING & LINTING |
| description | Specialized rules for repairing Markdown lint errors in Gold Context files (MD025, MD060, MD024). |
Version: Gold v1.0
Type: Utility Skill
Tier: 3 — Loaded when requested or encountering linting errors in context files
File: skills/context-formatting/SKILL.md
Primary Mode: Builder (formatting/fixing)
Purpose: Automates the correction of common Markdown linting errors generated in Gold Context Files, specifically targeting the metadata block (MD025), tight table separators (MD060), and recurring "Guidance" headings (MD024).
contexts/*.md files.When instructed to format a new context file, immediately apply these three transformations using the multi_replace_file_content tool.
The context file templates frequently arrive with metadata formatted as H1 tags at the top of the file, directly underneath the primary title. This triggers MD025 because markdown files should only have a single # H1 heading.
Action: Convert all secondary metadata hashes into bold markdown descriptors. Fix any broken line continuations.
From:
**Version:** Gold v2.0
**Type:** Context File
To:
**Version:** Gold v2.0
**Type:** Context File
| The context templates use compressed table alignment pipes without proper whitespace (e.g., | -------- | ------- |). The markdown linter requires spaces around the pipes for aligned column styles. |
| Action: Replace tight table separators with standard spaced separators (| --- |). Do this for EVERY table in the file. |
From:
| Metric | Current Value | Target | Why It Matters |
| --- | --- | --- | --- |
To:
| Metric | Current Value | Target | Why It Matters |
| --- | --- | --- | --- |
Context templates strategically repeat section headings like ### Guidance for Anti-Gravity or ### [Flow Name] across multiple sections. Markdown linters flag this as an MD024 collision.
Action: Suffix the duplicate heading with a parenthetical descriptor tied to its parent section, making it unique across the document.
From:
## FRONTEND STACK
...
### Guidance for Anti-Gravity
To:
## FRONTEND STACK (SKILL: CONTEXT FORMATTING)
...
### Guidance for Anti-Gravity (Frontend)
| 1. Do not alter the primary content. Only touch the formatting tags (#, |---, and heading names). |
multi_replace_file_content tool call containing multiple ReplacementChunks whenever possible to save time.