Loading...
Loading...
Found 2,183 Skills
Structured logging strategy including log levels, correlation IDs, context propagation, and PII avoidance. Use when designing logging, reviewing log statements, or setting up log aggregation.
Use when the user needs research methodology, long-form content creation, academic-style citations, fact-checking, or evidence-based writing with proper source attribution. Trigger conditions: whitepaper drafting, research article writing, source evaluation, citation management, fact-checking protocol, case study creation, evidence-based argumentation.
This skill should be used when the user asks to "improve my setup", "learn from this session", "fix my config", "stop asking for permissions", or reports friction with skills, agents, hooks, or permissions. Analyzes conversation history and proposes configuration improvements.
Post-session retrospective: audits efficiency, proposes skill/memory/CLAUDE.md updates, and generates coaching feedback
Extracts the full design soul, system, and agent rules from reference UI images. Use this skill when the user provides screenshots, Figma exports, or any UI reference images and wants the agent to design with the same soul, taste, feeling, and personality — not just copy colors and spacing. Marrow reads beneath the surface: it extracts the living core of a design — the decisions, proportions, restraint, and emotional intent that make a UI feel the way it does. Triggers on: /marrow, /extract-ui, /design-from-ref, /read-design, or any prompt like "extract the design system from these images", "make it look and feel like this", "get the rules from this UI", "build with the same soul", "match this design". Always use this skill when images are provided alongside a request to replicate, match, or be inspired by a design.
Full project soul alignment in one command. Scans every frontend file in the project, builds a prioritized plan, then systematically aligns all components and styles to .marrow.md. Smart enough to detect if .marrow.md was updated since the last run and only reprocess files affected by what changed — not a full rewrite every time. Use this skill when the user wants to align the entire project to the design soul at once, just installed marrow mid-project and wants to catch everything up, or updated .marrow.md via /marrow-update and wants to propagate only the changed rules across the project. Triggers on: /marrow-redesign, or prompts like "align the whole project", "redesign everything to match marrow", "apply marrow to all files", "full soul alignment", "catch everything up to marrow", "propagate the marrow update", "marrow everything". Requires .marrow.md to exist. If not found, instructs user to run /marrow first. This is a multi-step agentic command — it will take multiple turns to complete large projects. It creates a .marrow-state.json file to track progress and enable smart diff on future runs.
Identify, disclose, and mitigate conflicts of interest in advisory and brokerage relationships under Reg BI and fiduciary duty. Use when the user asks about compensation-based conflicts, proprietary product incentives, revenue sharing disclosure, principal trading consent, soft dollar arrangements, pay-to-play restrictions, gifts and entertainment limits, personal trading policies, or code of ethics requirements. Also trigger when users mention 'is this a conflict', 'recommending our own funds', 'higher payout on annuities', 'outside business activity conflicts', 'allocation fairness across accounts', 'political contribution to a pension board member', or ask how to disclose or eliminate a conflict.
Process and manage account transfers between and within financial institutions. Use when handling full or partial ACAT transfers between broker-dealers, troubleshooting ACAT rejection codes or FINRA Rule 11870 timeline issues, setting up non-ACAT transfers like mutual fund direct transfers or DTC free deliveries, processing internal journal entries to move assets between accounts, handling retirement account rollovers or Roth conversions with proper tax reporting, managing estate transfers with cost basis step-up and date-of-death valuations, reconciling assets after transfer completion including residual credits and fractional shares, coordinating multi-account household transfers across different account types, or building transfer tracking dashboards and client communication workflows.
Reusable UI blocks built with SGDS components and utilities that can be mixed and matched inside any page template. Use this skill whenever a user asks about app layout, application shell, page structure, sticky header, masthead placement, mainnav placement, footer placement, sgds-container, sgds-container-sidebar, simple app layout, sidebar app layout, dashboard layout, filter panel, sidebar filter, category filter, checkbox filter, or any self-contained UI section — even if they don't name it a 'block'. These are drop-in sections and shell structures, not full pages. Compose them with sgds-pattern-page-templates to build complete pages.
Audit top-level documentation (README, SPEC, PRODUCT) against recent git history to find drift — shipped features missing from docs or features listed as upcoming that already landed. Proposes minimal edits, creates a branch, and opens a PR. Use when asked to review docs for accuracy, after major feature merges, or on a periodic schedule.
Use when writing modern PHP 8.x code — enums, fibers, readonly properties, PSR standards, Composer, static analysis, SOLID patterns. Trigger conditions: PHP code authoring, enum design, readonly DTO creation, PSR-4 autoloading setup, PHPStan or Psalm configuration, PHP CS Fixer or Pint setup, Composer dependency management, SOLID principle application, type safety improvements, custom exception hierarchies, interface-driven design.
Brainstorm football data visualisations and chart designs. Use when the user wants ideas for how to visualise football data, needs inspiration for chart types, wants to explore design approaches for match reports, player profiles, team dashboards, or any football analytics graphic. Searches the web for popular approaches and real-world examples before proposing options.