Rajit Saha

You are a release engineer. Execute each phase in order. Each must fully complete before advancing. Do NOT ask for permission. Do NOT skip phases.

日本語の概要は準備中です。原文の説明を表示しています。

You are a security engineer. Auto-detect package managers, scan for vulnerabilities and leaked secrets, fix what's fixable, report the rest. Covers the dependency tree and tracked files — reviewing a pending diff's security belongs to a platform-native security-review skill when present.

日本語の概要は準備中です。原文の説明を表示しています。

You are a senior test engineer. Auto-detect all test layers (unit, integration, frontend, backend, E2E/system), run them all, write more if coverage is below threshold, and loop until everything passes.

日本語の概要は準備中です。原文の説明を表示しています。

Translate any technical specification into five precise, self-contained Figma Make prompts ready to paste and generate. Use when you have an enterprise-design, visual-system-architect, or copywriting output and need to convert it into Figma Make–compatible prompts covering hero, features, social proof, CTA, and mobile views.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to optimize any form that is NOT signup/registration — lead capture, contact, demo request, application, survey, or checkout forms; "form friction," "form completion rate," "form abandonment," "too many fields," "nobody fills out our form." For signup/registration forms, see signup-flow-cro. For popups containing forms, see popup-cro.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to plan or build a free tool for marketing — "engineering as marketing," "lead gen tool," "ROI calculator," "generator," "grader tool," "audit tool," "should I build a free tool," or giving away something useful to attract leads or links. For content-based lead generation, see content-strategy.

日本語の概要は準備中です。原文の説明を表示しています。

Run the pre-commit quality gate: test coverage, security scan, local build, plus Docker and cloud checks when applicable. Use before any commit or push; a failing gate blocks both.

日本語の概要は準備中です。原文の説明を表示しています。

Act as a Senior Frontend Systems Engineer to architect interactive modules — multi-step forms, pricing calculators, faceted search, dashboards, and auth flows. Defines state machines, data flow, error handling, and React component structure. Use when designing complex UI logic for Figma Make prototypes or React implementation.

日本語の概要は準備中です。原文の説明を表示しています。

You are a senior engineering lead and product architect. Given an observation, bug, or gap, conduct a thorough multi-dimensional investigation, find the root cause, plan the resolution, and create a detailed actionable GitHub issue.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to plan a product launch, feature announcement, or release strategy — 'Product Hunt,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'launch checklist,' 'GTM plan,' 'we're about to ship.' For ongoing marketing after launch, see marketing-ideas.

日本語の概要は準備中です。原文の説明を表示しています。

You are a release engineer. Execute each phase in order. Each must fully complete before advancing. Do NOT ask for permission. Stop only if something is truly unfixable.

日本語の概要は準備中です。原文の説明を表示しています。

Detect the project's linters and formatters, run them, and fix every error. Use when asked to lint or clean up style and type errors.

日本語の概要は準備中です。原文の説明を表示しています。

When the user needs marketing ideas, inspiration, or growth strategies for their SaaS or software product — 'how to market,' 'ways to promote,' 'what else can I try,' 'no idea how to market this,' 'brainstorm marketing.' The starting point when someone is stuck on growth. For channel execution, see the relevant skill (paid-ads, social-content, email-sequence, etc.).

日本語の概要は準備中です。原文の説明を表示しています。

Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.

日本語の概要は準備中です。原文の説明を表示しています。

Act as a Senior Motion Designer to specify and ship purposeful UI animation — micro-interactions, transitions, scroll-driven sequences, page transitions, loading states. Outputs easing/duration tokens, Framer Motion + GSAP recipes, and prefers-reduced-motion strategies. For implementing with the Motion/Framer Motion library itself, prefer a motion-framer plugin skill when present; use this for the motion design spec and audit.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value — "activation rate," "empty states," "onboarding checklist," "aha moment," "users sign up but don't use the product." Use when users sign up but don't stick around. For signup/registration optimization, see signup-flow-cro. For email sequences, see email-sequence.

日本語の概要は準備中です。原文の説明を表示しています。

Apply the Workflow Orchestration methodology for complex, multi-step tasks — plan-first approach, subagent strategy, self-improvement loop, verification before done, elegant solutions, and autonomous bug fixing. Use for any non-trivial task with 3+ steps or architectural decisions.

日本語の概要は準備中です。原文の説明を表示しています。

Install, list, or uninstall optional vendor skill packs not bundled by default — "add the Databricks pack", "what packs are available", "is there a pack for X", "get me the Databricks skills".

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to increase conversions on any marketing page — homepage, landing, pricing, feature, or blog; "CRO," "this page isn't converting," "low conversion rate," "bounce rate," "my landing page sucks" — or just shares a URL asking for feedback. For signup flows, see signup-flow-cro; post-signup activation, onboarding-cro; forms, form-cro; popups, popup-cro.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants help with paid advertising on Google Ads, Meta, LinkedIn, or Twitter/X — 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'retargeting,' 'audience targeting,' 'ad budget,' 'should I run ads.' Covers campaign strategy, targeting, bidding, and optimization. For bulk ad creative, see ad-creative. For landing pages, see page-cro.

日本語の概要は準備中です。原文の説明を表示しています。

Coder<->reviewer handoff loop (claude/codex/cursor/pi, roles swappable) with self-instrumented per-round cost tracking. Loops locally via HANDOFF.md until approved, then opens a PR with the full transcript.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates — "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached," "free users won't upgrade." Covers in-product upgrade moments where the user has already experienced value — distinct from public pricing pages (see page-cro). For pricing decisions, see pricing-strategy.

日本語の概要は準備中です。原文の説明を表示しています。

When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion — "exit intent," "lead capture popup," "email popup," "announcement banner," "scroll trigger," "sticky bar," or any interrupt-style conversion element. For forms outside popups, see form-cro. For page-level conversion, see page-cro.

日本語の概要は準備中です。原文の説明を表示しています。

Create a GitHub Pull Request with full AI review. Human approves and merges.

日本語の概要は準備中です。原文の説明を表示しています。