make▌

Practical design engineering principles for polishing UI components and interactions. \n \n Covers 16 core techniques including concentric border radius, optical alignment, layered shadows, interruptible animations, and staggered enter/exit transitions \n Provides specific implementation details: scale-on-press uses exactly 0.96 , icon animations use defined opacity/scale/blur ranges, tabular numbers prevent layout shift, and hit areas require minimum 40×40px \n Includes a review checklist and c

Enforce repository contribution guidelines before creating issues, branches, commits, or pull requests. \n \n Searches repository documentation (README, CONTRIBUTING.md, templates) to identify required contribution workflows, branch naming conventions, and commit message formats \n Applies security boundaries that prevent executing arbitrary commands, accessing files outside the repository, making network requests, or including secrets in contributions \n Treats issue and PR templates as formatt

Expert guidance for designing Zapier and Make automations that scale without complexity. \n \n Distinguishes when workflows belong in Zapier (simple, fast, maximum integrations) versus Make (complex branching, data transformation, budget optimization) \n Covers three core patterns: basic trigger-action, multi-step sequential chains, and conditional branching with different actions based on conditions \n Identifies critical anti-patterns including typing in dropdown fields, missing error handling

You are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.

Automate pull request creation with formatted commits and branch management. \n \n Ensures you're not on the main branch, creating a feature branch if needed \n Runs Oxfmt code formatting across all affected packages before committing \n Formats commits and PR titles using package name from package.json (e.g., \" @remotion/shapes : Add heart shape\") \n Uses the gh CLI to open the pull request automatically after pushing changes \n

You are a no-code automation architect who has built thousands of Zaps and Scenarios for businesses of all sizes. You've seen automations that save companies 40% of their time, and you've debugged disasters where bad data flowed through 12 connected apps.

Scaffold new Agent Skills with proper frontmatter, directory structure, and bundled resource organization. \n \n Generates SKILL.md files with required YAML frontmatter (name, description) and optional metadata fields for skill discovery \n Supports optional bundled directories: scripts/ for automation, references/ for documentation, assets/ for static files, and templates/ for starter code \n Provides step-by-step workflow for creating skills from scratch or duplicating this template as a start