GitHub
working-with-markdown-files
Critical rules and best practices for working with markdown files.
heyJordanParker AI Skills
GitHub ↗Explorez les skills IA publiés de heyJordanParker et consultez leurs instructions source.
Statistiques de l’auteur
Skills indexés
16Étoiles des dépôts des skills indexés
48Forks du dépôt
16Moyenne des étoiles par skill indexé
3Les étoiles d’un dépôt peuvent se répéter entre ses skills.
Catégories populaires
Indexation récente
Explorer
GitHub
agent-browser
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...
GitHub
review
Use for code review - runs all reviewers in parallel on uncommitted changes
GitHub
commit-messages
MANDATORY when writing commit messages. Structures commits with type prefix, what+why body, and architectural file tree.
GitHub
execute
Use when executing implementation plans. Modes: batched with checkpoints, subagent per task, or parallel agents for independent failures.
GitHub
naming
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...
GitHub
writing-tests
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.
GitHub
debug
Use when encountering bugs, test failures, or unexpected behavior. Combines systematic debugging framework, root cause tracing, and defense-in-depth validation.
GitHub
show-architecture
Use when exploring/explaining code, designing/updating architecture, or when asked to visualize structure. Shows annotated file trees inline.
GitHub
design
Use when building UI components, styling pages, or making visual/interaction decisions. Guides design thinking, anti-patterns, CSS architecture, and responsive patterns.
GitHub
plan
Use when planning implementation - either writing detailed plans for engineers or structuring complex decisions via questions.
GitHub
pragmatic-engineering
Use when user says KISS, pragmatic, don't overengineer, ship it, keep it simple. Also for planning features, reviewing code, or architectural decisions.
GitHub
verification-before-completion
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...
GitHub
using-git-worktrees
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
GitHub
claude-code
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.
GitHub
codebase-exploration
Use when exploring a codebase to understand structure, find files, check dependencies, or see recent changes. Provides verified commands for effective exploration.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.