Skill category
Use this category when you need Claude Code guidance that is specific to a language or framework conventions, toolchain, and ecosystem.
Profiles optimized for specific languages or frameworks: TypeScript, Next.js, Python, and more.
Use the hub when you need a wider choice set, review methodology, or a different workflow path. Return to the skills overview
Use this profile when the repo is TypeScript-first and you want the agent to respect tsconfig boundaries, type inference, strictness, and the build scripts that already define correctness.
3 source signals • Last reviewed 2026-04-01
Do not weaken strict compiler settings just to make an AI-generated patch pass quickly.
Use this profile when the repository is built on Next.js App Router and you want Claude Code to follow the framework's routing, data-fetching, and server-client boundaries correctly.
3 source signals • Last reviewed 2026-04-01
Do not blur server-only and client-only code paths when moving logic across App Router boundaries.
Use this profile when the main question is which MCP servers to add and how they fit into a Claude Code workflow. It helps when a team is moving from simple chat usage toward tool-connected automation.
1 source signals • Last reviewed 2026-04-02
Every MCP server is part of the trust boundary, so confirm what data, commands, and auth surfaces it exposes before enabling it.
Use this profile when you are building an app experience that depends on MCP rather than only adding one server. It fits teams shaping product flows where Claude Code or another agent coordinates multiple MCP-backed capabilities.
1 source signals • Last reviewed 2026-04-02
When an app combines multiple MCP tools, keep capability boundaries explicit so one prompt path does not gain accidental access to everything.
Use this profile when Claude Code or another agent needs to participate in a Power Automate oriented toolchain through MCP. It is useful for teams bridging agent workflows with enterprise automation systems.
1 source signals • Last reviewed 2026-04-02
Power Automate style integrations often touch business systems, so audit the downstream actions an MCP trigger can invoke.
Use this profile when the work is about authoring an MCP integration from scratch or shaping a new server around existing systems. It is useful for developers who need Claude-compatible tooling that does not exist yet.
1 source signals • Last reviewed 2026-04-02
Keep the server interface as small as possible so the agent only gets the actions and data it truly needs.
Use this profile when an agent workflow needs payment-related capabilities through MCP rather than only local dev tools. It is useful for builders connecting commerce or transaction flows to Claude-compatible tooling.
1 source signals • Last reviewed 2026-04-02
Treat any payments-related MCP surface as high risk because even small mistakes can trigger real financial side effects.
Use this profile when an MCP integration needs to represent checkout steps inside a commerce workflow. It is useful for builders exposing purchase actions to agents in a more structured way.
1 source signals • Last reviewed 2026-04-02
Checkout-related MCP tools should be treated as transactional surfaces, not general-purpose convenience actions.
Use this profile when an agent needs to participate in checkout flows through a dedicated commerce MCP toolset. It helps when you want checkout steps to be agent-addressable without opening up the entire commerce system.
1 source signals • Last reviewed 2026-04-02
Treat checkout actions as high-sensitivity operations and require clear environment boundaries between test and production.
Use this profile when an agent needs MCP-mediated access in browser-heavy or web automation contexts. It fits teams connecting interactive web workflows to model-accessible tools.
1 source signals • Last reviewed 2026-04-02
Browser-facing bridges can cross several trust boundaries at once, so review what page data and what tool actions become reachable together.
Use this profile when MCP needs to support Canvas app configuration or similar low-code admin flows. It is helpful for teams bringing app-configuration work into an agent-friendly tool surface.
1 source signals • Last reviewed 2026-04-02
Administrative app configuration surfaces can alter shared environments quickly, so scope tools to the minimal set of safe operations.
Need broader discovery? Skills overview
Need OpenClaw context? OpenClaw workflow