working-with-markdown-files
Critical rules and best practices for working with markdown files.
浏览 heyJordanParker 维护的已发布 AI 技能,比较用途与说明,并通过来源仓库了解安装方式。
已收录技能
16收录技能的仓库 Stars 合计
48仓库 Forks
16平均每个技能的仓库 Stars
3同一仓库中的多个技能可能共享 Stars,合计包含重复仓库数据。
Critical rules and best practices for working with markdown files.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web appl...
Use for code review - runs all reviewers in parallel on uncommitted changes
MANDATORY when writing commit messages. Structures commits with type prefix, what+why body, and architectural file tree.
Use when executing implementation plans. Modes: batched with checkpoints, subagent per task, or parallel agents for independent failures.
MANDATORY for all naming decisions - variables, functions, files, folders, classes, database tables, routes, CSS classes. Must be followed when creating or renaming any identifier. Non-negotiable baseline for c...
MANDATORY when writing tests. Test behavior, not implementation. Functional tests are primary. Unit tests ONLY for state mutations. Includes fixing flaky tests with condition-based waiting.
Use when encountering bugs, test failures, or unexpected behavior. Combines systematic debugging framework, root cause tracing, and defense-in-depth validation.
Use when exploring/explaining code, designing/updating architecture, or when asked to visualize structure. Shows annotated file trees inline.
Use when building UI components, styling pages, or making visual/interaction decisions. Guides design thinking, anti-patterns, CSS architecture, and responsive patterns.
Use when planning implementation - either writing detailed plans for engineers or structuring complex decisions via questions.
Use when user says KISS, pragmatic, don't overengineer, ship it, keep it simple. Also for planning features, reviewing code, or architectural decisions.
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before as...
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
Use when working with Claude Code itself - skills, agents, commands, hooks, settings, documentation. Alias "cc". Covers building, testing, sharing skills, updating Claude.md files, and context engineering.
Use when exploring a codebase to understand structure, find files, check dependencies, or see recent changes. Provides verified commands for effective exploration.
默认按已收录数据中的 GitHub 仓库 Stars 排序。Stars 属于来源仓库,同一仓库的多个技能可能共享相同数值;它反映仓库关注度,不代表单个技能的安装量或质量评分。