Coding & Dev Tools

maplin-co Skill

Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes

tomazwang Skill

Comprehensive code review with parallel specialized agents

tomazwang Skill

Flexible AI-assisted brainstorming for any creative challenge

tomazwang Skill

Systematic code review skill for providing constructive feedback

tomazwang Skill

Interactive wizard for creating Claude Code skills with proper structure and frontmatter

tomazwang Skill

Interactive plugin creation wizard - guides you through scaffolding a new Claude Code plugin

tomazwang Skill

Browse skill templates for common patterns

tomazwang Skill

Validate design documents for completeness, clarity, and feasibility

tomazwang Skill

Implementing event hooks for PreToolUse, PostToolUse, SessionStart, and other events

tomazwang Skill

How to create effective skills with proper triggering conditions and structure

ahgraber Bundle

Use when writing or reviewing tests in any language, or diagnosing a suite that is slow, brittle, or hard to read. Triggers: "write tests", "how should I test this", "what kind of test", "test is flaky/fragile", "should I mock this", "test is hard to read". Python-specific practices (mocking, pytest, async) are included in `references/python-testing.md`.

ahgraber Bundle

Use whenever a Conventional Commit message is being drafted — whether the user asks ("write commit message", "draft commit from staged changes", "generate conventional commit", "split this into commits") or you are about to propose one proactively after finishing work (e.g. completing tasks, wrapping up a feature, or summarizing staged changes). Invoke before writing the message inline. Not for creating commits, amending history, or full code review.

ahgraber Skill

Use when the user wants rigorous, non-sycophantic editorial feedback on a draft, essay, blog post, or argument through back-and-forth dialogue — pressure-testing thesis, structure, argument, clarity, tone, and evidence. Triggers: "be my sparring partner", "pressure-test this draft", "poke holes in my argument", "is this ready to publish", "sharpen this post", "where is this weak". Not for one-shot copyediting, proofreading, or ghostwriting.

ahgraber Bundle

You MUST use this when receiving feedback that evaluates a text-based work artifact you produced or are responsible for — code, specs, design docs, PRDs, proposals, plans, or prose — by asserting a defect, questioning a decision, supplying reasoning, or proposing a change for assessment. Also use when asked to implement external review comments that must first be assessed. Not for an unambiguous parameter choice, approval, confirmation, typo or formatting fix, or direct revision instruction that supplies no claim or rationale to evaluate.

ahgraber Bundle

Use when writing or reviewing asyncio code in Jupyter notebooks or '#%%' cell workflows — structuring event-loop ownership, orchestrating async tasks, or choosing compatibility strategies. Also use when hitting RuntimeError: This event loop is already running, asyncio.run() failures in cells, or tasks silently never completing.

serpro69 Bundle

Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.

maplin-co Skill

Use when persisting learnings, loading previous context, or searching past decisions - covers memory file structure, tools, and when to update each file

maplin-co Skill

Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge

maplin-co Skill

Use when you've developed a broadly useful skill and want to contribute it upstream via pull request - guides process of branching, committing, pushing, and creating PR to contribute skills back to upstream repository

maplin-co Bundle

Chrome DevTools for debugging, performance analysis, and browser automation. Use when debugging web apps, analyzing performance, inspecting network requests, or automating browser interactions.

maplin-co Skill

Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches

maplin-co Skill

Use when invalid data causes failures deep in execution, requiring validation at multiple system layers - validates at every layer data passes through to make bugs structurally impossible

maplin-co Bundle

Use when errors occur deep in execution and you need to trace back to find the original trigger - systematically traces bugs backward through call stack, adding instrumentation when needed, to identify source of invalid data or incorrect behavior

maplin-co Skill

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

maplin-co Skill

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes - four-phase framework (root cause investigation, pattern analysis, hypothesis testing, implementation) that ensures understanding before attempting solutions

maplin-co Skill

Use when writing or changing tests, adding mocks, or tempted to add test-only methods to production code - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies

maplin-co Bundle

Use when completing tasks, implementing major features, or before merging to verify work meets requirements - dispatches review subagent to review implementation against plan or requirements before proceeding

maplin-co Bundle

Use when tests have race conditions, timing dependencies, or inconsistent pass/fail behavior - replaces arbitrary timeouts with condition polling to wait for actual state changes, eliminating flaky tests from timing guesses

maplin-co Skill

Use when implementing any feature or bugfix, before writing implementation code - write the test first, watch it fail, write minimal code to pass; ensures tests actually verify behavior by requiring failure first

maplin-co Skill

Use when facing 3+ independent failures that can be investigated without shared state or dependencies - dispatches multiple Claude agents to investigate and fix independent problems concurrently

matsuni-kk Bundle

validate_skills.pyを実行してSkills/Agents/Commandsの構文を検証し、エラーを修正してログを記録する。「バリデーション」「構文検証」「Skillsチェック」を依頼されたときに使用する。

matsuni-kk Bundle

Skills版エージェント骨格（CLAUDE.md, .cursor/skills/, .codex/等）を生成し、初期設定を完了する。「スケルトン生成」「エージェント生成」「骨格作成」を依頼されたときに使用する。

matsuni-kk Bundle

Skills群に対応するサブエージェント（.claude/agents/*.md）を設計・生成する。「サブエージェント作成」「並列処理エージェント」「専門エージェント」を依頼されたときに使用する。

matsuni-kk Bundle

ドメイン要件と業界標準フレームワークに基づき、対象エージェント用のSkills群（SKILL.md/assets/evaluation/questions）を設計・生成する。「Skills作成」「ワークフロー群生成」「機能実装」を依頼されたときに使用する。

akaihola Bundle

Query Helsinki region public transport routes and departures via HSL/Digitransit. Use when the user asks about HSL timetables, next departures, route planning, stops, stations, trams, metro, buses, ferries, or local train connections in the Helsinki region.

akaihola Skill

Extract actionable learnings from this conversation and persist them where they will be found again.