Sheshiyer
- 721 skills
- 0 followers
- 1 day ago last updated
- ▌ Redis Patterns · sheshiyerRedis data structures, caching strategies, distributed locks, rate limiting, pub/sub, and connection pooling for production. USE WHEN adding caching, implementing rate limiting or locks, or designing Redis-backed workflows.
- ▌ Secret Scanner · sheshiyer bundleScan codebases for leaked secrets, API keys, and credential exposure patterns. USE WHEN before pushing to a public repo, during a security audit, or wiring secret detection into CI/CD.
- ▌ Social Content · sheshiyer bundleWhen the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' or 'grow my following.' Use this for any social media content creation, repurposing, or scheduling task. For broader content strategy, see content-strategy.
- ▌ Threejs Skills · sheshiyerCreate high-quality 3D scenes and interactive experiences with Three.js best practices — scene setup, lighting, controls, animation loops, and effects. USE WHEN building Three.js/WebGL graphics, 3D visualizations, or interactive scenes.
- ▌ Upgrading Expo · sheshiyer bundleGuidelines for upgrading Expo SDK versions and fixing the dependency issues that follow. USE WHEN bumping an Expo SDK (including beta/preview releases), running expo-doctor, or resolving New Architecture, React 19, or native-tabs migration breakage after an upgrade.
- ▌ Upstash Qstash · sheshiyerUpstash QStash expert for serverless message queues, scheduled jobs, and reliable HTTP-based task delivery without managing infrastructure. USE WHEN you need serverless cron, webhook delivery with retries/signature verification, delayed jobs, or HTTP-based message queuing via QStash.
- ▌ Accesslint Diff · sheshiyerDiff a live page's accessibility violations against a baseline — by default compares uncommitted changes (stash-based), or pass --branch [<name>] to diff against a branch; reports only new violations introduced, violations fixed, and pre-existing count. USE WHEN you want to prove a UI change adds no new WCAG violations before a PR, or to separate a11y issues a diff introduced from pre-existing ones (use accesslint-scan for a full audit with no diffing).
- ▌ Accesslint Scan · sheshiyerAudit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing. USE WHEN you want a full a11y audit of a running page or preview URL and a prioritized fix list (use accesslint-diff instead when you only want violations a change introduced).
- ▌ Astro Framework · sheshiyer bundleAstro framework specialist for building fast, content-driven websites with islands architecture. Use when creating Astro components, configuring hydration (client:load/idle/visible/media), using server:defer (server islands), Content Layer API (glob/file loaders, live loaders), sessions, astro:env, i18n routing, actions, SSR adapters, view transitions, or integrating React/Vue/Svelte/Solid. Not for full-SPA frameworks (Next.js, Remix, SvelteKit).
- ▌ Azure Functions · sheshiyerAzure Functions patterns — isolated worker model, Durable Functions orchestration, cold-start optimization, production hardening across .NET, Python, and Node.js. USE WHEN building, orchestrating, or optimizing Azure Functions apps (durable workflows, triggers/bindings, cold starts).
- ▌ Cloudflare Core · sheshiyerShared reference for the Cloudflare cluster: the edge-compute + binding model every Worker turns on, wrangler.jsonc conventions, compatibility_date, the storage-primitive decision matrix (KV vs R2 vs D1 vs Durable Objects), secrets, and the auth-token gotcha. USE WHEN adding a binding, choosing a storage primitive, writing wrangler config, or debugging a Cloudflare deploy — the interlocking rules every Cloudflare spoke shares.
- ▌ Conducty Review · sheshiyerEnd-of-plan review sweep. Audits the plan's executed prompts, records verdicts with evidence, extracts failure patterns, computes velocity metrics, prepares carry-forward intelligence. Use when the user says "review", "audit", "review this plan", or at the end of a plan before [[conducty-improve]].
- ▌ Conducty System · sheshiyerEstablishes the Conducty orchestration system — its philosophy, ten engineering-grounded principles, ubiquitous language, and per-plan cycle. USE WHEN starting any session before invoking other Conducty skills, or the user says "what is Conducty", "explain the system", or asks about the cycle / principles / vocabulary.
- ▌ Conducty Verify · sheshiyerThe evidence gate. Run the verification command via Bash, read the output, then make the claim. USE WHEN about to mark ANY prompt complete, before any "done" / "passed" claim, or the user asks to verify, confirm, or prove a result.
- ▌ Fp TS Pragmatic · sheshiyerA practical, jargon-free 80/20 guide to fp-ts functional programming for handling nullable values, errors, and async in TypeScript without category-theory overhead. USE WHEN writing or refactoring TypeScript with fp-ts (Option/Either/TaskEither).
- ▌ Frontend Slides · sheshiyer bundleCreate stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
- ▌ Git Pr Ops Core · sheshiyerShared reference for the git-pr-ops cluster: the gated review→prepare→merge pipeline, the `.local/` artifact handoff (review.json findings), head-SHA pinning, the push/merge safety rules (force-with-lease, no auto-merge, never push main), and the finding-severity contract. USE WHEN preparing or merging a GitHub PR, resolving review findings, or wiring the issue→PR flow — the interlocking rules every spoke shares.
- ▌ Growth SEO Core · sheshiyerShared reference for the growth-seo cluster: the search-intent model every task turns on, the one-query-per-page contract, the intent→content-type matrix, the E-E-A-T/quality bar, and the funnel pipeline. USE WHEN mapping keywords to pages, judging whether content will rank, planning programmatic pages, or deciding informational vs commercial vs transactional treatment.
- ▌ Healthcare Core · sheshiyerShared reference for the healthcare cluster: the three-layer data-protection contract (classify → access-control → audit), the patient-safety bias (alerts block, never silently pass), the alert-severity matrix, and the CRITICAL-vs-HIGH deploy-gate thresholds. USE WHEN handling PHI, designing clinical access control, wiring a CDSS alert, or configuring a safety gate — the interlocking rules every healthcare spoke shares.
- ▌ Hyperframes CLI · sheshiyerHyperFrames CLI dev loop — `npx hyperframes` for scaffolding (init), validation (lint, inspect), preview, render, and environment troubleshooting (doctor, browser, info, upgrade). Use when running any of these commands or troubleshooting the HyperFrames build/render environment. For asset preprocessing commands (`tts`, `transcribe`, `remove-background`), invoke the `hyperframes-media` skill instead.
- ▌ Langsmith Fetch · sheshiyerDebug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
- ▌ Marketing Ideas · sheshiyer bundleWhen the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (paid-ads, social-content, email-sequence, etc.).
- ▌ Native IOS Core · sheshiyerShared reference for the native-iOS cluster: the iOS 26 / Swift 6.2 / Xcode 26 baseline, availability-gating discipline for the new frameworks, the data-race-safety (actor isolation + Sendable) model, and shared SwiftUI conventions. USE WHEN adopting Swift 6.2 concurrency, gating an iOS 26-only API, or choosing a state/persistence pattern — the rules every native-iOS spoke shares.
- ▌ Pitchdeck Skill · sheshiyer bundleGenerate immersive, scrollytelling investor pitch experiences with glassmorphism UI, animated text effects, and parallel research agents. Use when users request pitch decks, investor presentations, business plan artifacts, or fundraising materials. Outputs IDE-ready project scaffolding (Overview.md, DesignSpec.md, Tasks.md) plus a React artifact preview. Leverages web search for market research and extended thinking for narrative strategy.
- ▌ Promptinjection · sheshiyer bundlePrompt injection testing. USE WHEN prompt injection, jailbreak, LLM security, AI security assessment, pentest AI application, test chatbot vulnerabilities.
- ▌ Resume Enhancer · sheshiyer bundleRewrite and optimize resumes for target roles with stronger impact bullets and ATS keyword alignment. USE WHEN a task matches the Craft workspace workflow for resume-enhancer.
- ▌ Selemene Report · sheshiyer bundleGenerate Selemene Engine reports from a slash-command. Routes deterministic birth/compatibility/transit reports through the existing @selemene/bridge CLI and narrative witness readings through the packages/witness-pipeline. USE WHEN the user says /selemene-report, selemene report, generate selemene report, birth chart report, compatibility report, transit report, or witness reading. NOT for building new engines, not for replacing the bridge CLI, not for human web UI intake.
- ▌ Senior Frontend · sheshiyer bundleSenior frontend workflows for React, Next.js, TypeScript, and Tailwind — scaffolding, component/hook generation, bundle analysis, patterns, a11y, testing. USE WHEN building, optimizing, or reviewing a React/Next.js frontend.
- ▌ Signup Flow Cro · sheshiyer bundleWhen the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding-cro. For lead capture forms (not account creation), see form-cro.
- ▌ Swarm Architect · sheshiyerUpgraded planning protocol for large-scale delivery plans: interactive discovery, 80-task default granularity, phase→wave→swarm orchestration, and dispatch-aware GitHub synchronization. USE WHEN you need a production-grade, heavily parallelized execution plan (70–80+ tasks) decomposed into phases, waves, and independently runnable swarms with explicit dependencies and verification gates.
- ▌ Terraform Skill · sheshiyerTerraform & OpenTofu infrastructure-as-code best practices — module hierarchy, testing (validate/plan/frameworks), multi-environment structure, state management, and CI/CD. USE WHEN authoring, structuring, testing, or reviewing Terraform/OpenTofu configs and modules.
- ▌ Transformers JS · sheshiyer bundleRun Hugging Face models in JavaScript or TypeScript with Transformers.js, in Node.js or the browser (including WebGPU). USE WHEN running ML inference client-side or in Node with Transformers.js.
- ▌ Vercel Optimize · sheshiyer bundleObservability-first Vercel optimization audit — pull production metrics, gate investigations deterministically, and emit version-aware cost/perf recommendations. USE WHEN auditing a deployed Vercel app for cost or performance issues.
- ▌ Accesslint Audit · sheshiyerFind and fix WCAG 2.2 accessibility issues in code or live pages, in report mode (prioritized written audit, no edits) or fix mode (audit->edit->verify), preferring direct-CDP live-DOM auditing. USE WHEN an agent's UI output needs an accessibility audit or WCAG fixes before shipping.
- ▌ Agent Evaluation · sheshiyerTest and benchmark LLM agents with behavioral contract testing, capability assessment, statistical/adversarial evaluation, regression pipelines, and production monitoring. USE WHEN you need to measure, benchmark, or regression-test an LLM agent's real-world reliability.
- ▌ Agentic Ops Core · sheshiyerShared reference for the agentic-ops cluster: the evidence-first operator loop (resolve surface → read live state → smallest reversible action → prove it → report exact status), the surface taxonomy, the status-word vocabulary, and the secrets/PII guardrails every operator spoke obeys. USE WHEN operating any live external surface — inbox, repo, tracker, billing, docs — or before any send/push/refund/mutation in this cluster.
- ▌ Churn Prevention · sheshiyer bundleWhen the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.
- ▌ Company Research · sheshiyer bundleCreate a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
- ▌ Conducty Context · sheshiyerIngest a project directory into the Obsidian vault as a linked context sub-graph — Architecture, Conventions, Invariants, Hotspots, Tests, Glossary, plus per-bounded-context module notes. Tracks refresh deltas over time, flags stale context, and feeds prompt generation via backlinks. Use when the user says "load context", "refresh context", "ingest project", "update context for X", or provides a directory path to analyze.
- ▌ Conducty Execute · sheshiyer bundleDispatches Claude Code Task subagents to run prompts from a vault plan note. Tracer-first execution, time-budgeted work, calibrated review rigor. Use when the user says "execute the plan", "run group A", "dispatch", or is ready to run prompts from a `Plans/Plan YYYY-MM-DD HHmm` note in the vault.
- ▌ Conducty Improve · sheshiyerEnd-of-plan improvement kata. Extracts lessons from the just-finished plan, identifies experiments, and shapes the next plan's approach. USE WHEN [[conducty-review]] has just completed, or the user says "what did we learn", "improve the process", "retrospective", "wrap up this plan".
- ▌ Deploy To Vercel · sheshiyer bundleDeploy applications and websites to Vercel, preferring git-push preview deploys and proper project linking. USE WHEN the user says deploy my app, push this live, give me a link, or make a preview deployment.
- ▌ Jvm Orchestrator · sheshiyerRoute a JVM task to the right skill among 16 specialists — Kotlin language/coroutines/Exposed/Ktor, Java coding standards, the Spring Boot stack (patterns, TDD, security, verification), the Quarkus stack (patterns, TDD, security, verification), JPA/Hibernate, and Compose Multiplatform UI. USE WHEN a user is building, testing, securing, or shipping a Kotlin or Java service but hasn't named the framework or the specific concern.
- ▌ Openai Image Gen · sheshiyer bundleBatch-generate images via the OpenAI Images API, with a random prompt sampler and an index.html gallery. USE WHEN producing many images at once with OpenAI (DALL-E / gpt-image), sampling varied prompts in bulk, or generating a browsable image gallery.
- ▌ PHP Laravel Core · sheshiyerShared reference for the Laravel cluster: the layered request flow (controller → service → action → model), typed Eloquent + Form Request validation, the standard JSON response envelope, the test/CI matrix, and the version/tooling baseline. USE WHEN structuring controllers, writing validation, wiring the test/verify pipeline, or choosing tooling — the conventions every Laravel spoke shares.
- ▌ Plan Orchestrate · sheshiyerRead a plan document, decompose it into steps, design a per-step agent chain from the available agent catalogue, and emit ready-to-paste /orchestrate custom prompts. Generative only — never invokes /orchestrate itself. Use when the user has a multi-step plan and wants to drive it through orchestrate without composing chains by hand.
- ▌ Pricing Strategy · sheshiyer bundleWhen the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywall-upgrade-cro.
- ▌ Programmatic SEO · sheshiyer bundleWhen the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.
- ▌ Project Flow Ops · sheshiyerOperate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
- ▌ Prompt Optimizer · sheshiyerAnalyze raw prompts, identify intent and gaps, match available agent components (skills/commands/agents/hooks), and output a ready-to-paste optimized prompt; advisory only. USE WHEN the user asks to optimize, improve, or rewrite a prompt; NOT FOR executing the task directly or optimizing code/performance.
- ▌ Referral Program · sheshiyer bundleWhen the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch-strategy.
- ▌ Sales Enablement · sheshiyer bundleWhen the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.
- ▌ Smart Goal Coach · sheshiyer bundleConvert broad ambitions into SMART goals with milestones, accountability, and review rhythm. USE WHEN a task matches the Craft workspace workflow for smart-goal-coach.
- ▌ 3d Web Experience · sheshiyerBuild 3D experiences for the web with Three.js, React Three Fiber, Spline, WebGL, and GLSL — product configurators, immersive sites, interactive scenes. USE WHEN adding 3D, a configurator, or WebGL depth to a web UI.
- ▌ AI Video Director · sheshiyer bundleCreate AI-generated video content using Kling 3.0 (multi-shot sequences with dialogue), Sora (scene generation with character consistency), or Grok (restricted content). Use when writing shot-by-shot video prompts, building character-consistent animated series, or routing between video generation tools.
- ▌ Angular Developer · sheshiyer bundleGenerate Angular code and architectural guidance covering signals reactivity, forms, dependency injection, routing, SSR, ARIA, animations, styling, testing, and CLI tooling. USE WHEN creating Angular projects, components, or services, or applying modern Angular best practices.
- ▌ Arch Orchestrator · sheshiyer bundleTurn a raw product brief into a consistent, implementation-ready spec pack under specs/ (frontend, backend, API, AI) by coordinating specialist agents and enforcing a project's preferred stack. USE WHEN the user says "create architecture plan/specs", "turn this brief into docs", "generate frontend/backend/api specs", or "write the spec markdown files" — wants end-to-end software architecture documentation from a product brief.
- ▌ Artifacts Builder · sheshiyer bundleBuild elaborate multi-component HTML artifacts with React, Tailwind CSS, and shadcn/ui, then bundle them into a single HTML file. USE WHEN a complex artifact needs state management, routing, or shadcn/ui components — NOT for simple single-file HTML/JSX artifacts.
- ▌ Autonomous Agents · sheshiyerBuild reliable autonomous agents that decompose goals, plan, execute tools, and self-correct, focusing on bounding failure probability across multi-step runs. USE WHEN making an unattended autonomous agent reliable rather than merely capable.
- ▌ Conducty Obsidian · sheshiyerConducty's context engine lives in an Obsidian vault. This skill defines the vault layout, naming, linking, and index conventions every other Conducty skill must follow when reading or writing notes. Use when reading/writing any plan, design, context, improvement, failure pattern, metrics, or prompt-log note — or when the user says "vault", "Obsidian", "context engine", "where is X stored".
- ▌ Customer Research · sheshiyer bundleWhen the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see page-cro.
- ▌ Data Storytelling · sheshiyerTransform data into compelling narratives using visualization, context, and persuasive structure. Use when presenting analytics to stakeholders, creating data reports, or building executive presentations.
- ▌ Devops Infra Core · sheshiyerShared reference for the devops-infra cluster: the read-only-by-default safety boundary every spoke turns on (diagnose → change-window → verify → rollback), the change-class taxonomy, shared conventions for evidence and isolation, and the tooling/version matrix. USE WHEN any infra task is about to mutate state — a device config, a firewall/VLAN rule, a container or cluster deploy — or when you need the conventions every devops-infra spoke shares.
- ▌ Electron Security · sheshiyerThe Electron hardening checklist — context isolation, sandbox, no nodeIntegration, strict CSP, navigation/window.open allowlists, IPC input validation, and safe handling of remote content. USE WHEN auditing or hardening an Electron app, reviewing webPreferences, or before shipping. Follows Electron's official security recommendations.
- ▌ Expo Orchestrator · sheshiyerRoute an Expo task to the right spoke across the app lifecycle — dev environment (dev client, NativeWind), Expo Router app-building, in-app API routes, native modules, EAS build/submit/update, and SDK upgrades. USE WHEN building or shipping an Expo / React Native app with the Expo toolchain but the specific step isn't named. For RN UI/animation/gesture craft that isn't Expo-specific, hand off to the react-native cluster.
- ▌ Frontend Web Core · sheshiyerShared reference for the frontend-web cluster: the rendering-model decision (CSR / SSR / RSC / static) that sets the hydration boundary, plus the conventions every spoke shares — the SSR/'use client' contract, the motion-foundations layering rule, the accessibility baseline, and the framework/tooling matrix. USE WHEN choosing a framework, wiring SSR-sensitive or motion code, or planning accessibility — the interlocking rules every frontend-web spoke depends on.
- ▌ Hugging Face Jobs · sheshiyer bundleRun workloads on Hugging Face Jobs with managed CPUs, GPUs, TPUs, secrets, and Hub persistence, with no local setup. USE WHEN you need to run a training or batch workload on managed Hugging Face cloud compute.
- ▌ Mobile IOS Design · sheshiyer bundleMaster iOS Human Interface Guidelines and SwiftUI patterns for building native iOS apps. USE WHEN designing iOS interfaces to Apple's HIG, laying out SwiftUI views/grids/navigation, choosing SF Symbols and Dynamic Type, or making an app feel native across iPhone and iPad (Dark Mode, accessibility, adaptive layout).
- ▌ Portfolio Builder · sheshiyer bundleDesign and structure role-specific portfolios that showcase evidence, outcomes, and credibility. USE WHEN a task matches the Craft workspace workflow for portfolio-builder.
- ▌ Postgres Patterns · sheshiyerPostgreSQL patterns for query optimization, schema design, indexing, and security, based on Supabase best practices. USE WHEN writing SQL queries or migrations, designing schemas, troubleshooting slow queries, implementing Row Level Security, or setting up connection pooling.
- ▌ Quality Eval Core · sheshiyerShared reference for the quality-eval cluster: the four quality gates (write → commit → CI → ship), the evidence ladder that says what proves a pass at each, pass@k vs a single green run, and the AI write-and-review blind spot. USE WHEN deciding what counts as done, choosing which gate catches a failure class, or wiring a measurement loop — the conventions every quality-eval spoke shares.
- ▌ Raycast Extension · sheshiyerBuild Raycast extensions with React and TypeScript. Use when the user asks to create a Raycast extension, command, or tool.
- ▌ Raycast UI Skills · sheshiyerRaycast's UI design system. Use when building interfaces inspired by Raycast's aesthetic - light mode, Inter font, 4px grid.
- ▌ React Native Core · sheshiyer bundleShared reference for the React Native cluster: the New Architecture (Fabric/TurboModules/JSI/bridgeless), styling approaches, navigation options, the Reanimated + Gesture Handler animation stack, platform differences, performance rules, and integrated product-flow audits. USE WHEN making RN UI/interaction decisions or reviewing whole-app flow gaps. Pairs with expo-core for the toolchain.
- ▌ React Performance · sheshiyerReact and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
- ▌ Rust Coding Skill · sheshiyer bundleIdiomatic, efficient, well-structured Rust authoring — data modeling (struct/enum/newtype, ownership choices), trait & impl organization, derive/declarative/proc macros, and build-speed best practices (mold, sccache, cargo check, workspaces). USE WHEN shaping Rust data structures, organizing impls/modules, writing macros, or tuning compile times.
- ▌ Rust Orchestrator · sheshiyerRoute a Rust task to the right skill — idiomatic patterns (ownership, errors, traits, concurrency, crate layout) versus testing (unit, integration, async, property-based, mocking, coverage, TDD). USE WHEN a user is writing, reviewing, refactoring, or testing Rust but hasn't named the specific concern.
- ▌ SEO Content Brief · sheshiyerUse when you need a structured search-intent brief from a topic, query cluster, offer, or URL — turning search demand into a brief downstream content and distribution agents can act on. USE WHEN the user asks for a content brief, search-intent brief, editorial plan, or packet-oriented content plan before writing.
- ▌ Slack Bot Builder · sheshiyerBuild Slack apps with the Bolt framework across Python, JavaScript, and Java — Block Kit UIs, interactive components, slash commands, event handling, OAuth installation flows, and Workflow Builder integration. USE WHEN building or productionizing a Slack app/bot, adding slash commands or interactive Block Kit UI, or wiring OAuth install flows.
- ▌ Social Media Core · sheshiyerShared reference for the social-media cluster: the adapt-don't-duplicate model, the draft-before-post approval contract, voice-profile reuse, the platform × format matrix, and the create→adapt→publish pipeline every spoke shares. USE WHEN adapting copy for more than one network, choosing a publish path, or producing an asset — the interlocking rules that keep the spokes consistent.
- ▌ Supply Chain Core · sheshiyerShared reference for the supply-chain cluster: the service-level vs landed-cost trade-off that every function optimizes, the SCOR stage map, the buffer/constraint model, common units (OTIF, fill rate, lead time, total landed cost), and the escalation matrix. USE WHEN setting safety stock, accepting a freight rate, sequencing production, or making a disposition/clearance call — the one objective all spokes share.
- ▌ Vercel Deployment · sheshiyerDeploy Next.js apps to Vercel — environment variables across environments, edge/serverless functions, build config, and production rollout. USE WHEN configuring or shipping a Next.js project on Vercel.
- ▌ Adaptability Coach · sheshiyer bundleDevelop adaptability in changing environments through scenario planning, fast feedback, and flexible execution. USE WHEN a task matches the Craft workspace workflow for adaptability-coach.
- ▌ Agent Tool Builder · sheshiyerDesign agent tools from JSON Schema to error handling and MCP exposure, writing LLM-legible descriptions, validation, and token-efficient interfaces that avoid silent failures. USE WHEN defining or hardening the tools/functions an LLM agent can call.
- ▌ AI Wrapper Product · sheshiyerTurn an AI API (OpenAI, Anthropic, etc.) into a focused, defensible, paid product — prompt engineering for products, usage metering, rate limiting, model selection, and output quality control. USE WHEN building or pricing an AI-wrapper business and you need it to solve a real problem rather than be a thin ChatGPT clone.
- ▌ Analytics Tracking · sheshiyer bundleWhen the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-test-setup.
- ▌ Astro Orchestrator · sheshiyerRoute an Astro task to the right spoke — building the site (components, islands/hydration, content, SSR, actions, i18n) or publishing a docs/wiki/press-kit site. USE WHEN working on an Astro project but the specific concern isn't named, or when deciding the rendering mode (static vs on-demand vs hybrid). For scroll/animation/video on an Astro page, hand off to the creative-frontend cluster.
- ▌ Awwwards UI Skills · sheshiyerAwwwards's UI design system. Use when building interfaces inspired by Awwwards's aesthetic - light mode, Inter font, 4px grid.
- ▌ Cloudflare Manager · sheshiyer bundleComprehensive Cloudflare account management for deploying Workers, KV Storage, R2, Pages, DNS, and Routes. Use when deploying cloudflare services, managing worker containers, configuring KV/R2 storage, or setting up DNS/routing. Requires CLOUDFLARE_API_KEY in .env and Bun runtime with dependencies installed.
- ▌ Conducty Bootstrap · sheshiyerFirst-run walkthrough for Conducty. Confirms vault location, seeds indexes if missing, ingests the user's primary project via [[conducty-context]], and produces a tiny scoped first plan so the user sees the cycle end-to-end. Use when the user says "set up Conducty", "first time", "get started", "bootstrap", "I just installed Conducty", or when no plans yet exist in the vault.
- ▌ Conducty Dialectic · sheshiyer bundleMulti-persona decision analysis through structured dialectic. Six software-engineering archetypes debate a question to uncover the Design Truth. Use when the user says "analyze this decision", "dialectic", "decision analysis", "think this through", "debate this", or faces an architectural/design choice.
- ▌ Conducty Worktrees · sheshiyerGit worktree lifecycle for parallel prompt execution. Creates isolated worktrees per prompt, verifies baselines, merges after checkpoint, cleans up. Use when a parallelization group has 2+ prompts targeting the same repo, or the user says "worktree", "isolate", "parallel branches".
- ▌ Free Tool Strategy · sheshiyer bundleWhen the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
- ▌ Headline Generator · sheshiyer bundleProduce high-performing headlines tailored to topic, audience intent, and platform context. USE WHEN a task matches the Craft workspace workflow for headline-generator.
- ▌ Signing Tauri Apps · sheshiyerCode-sign and notarize Tauri apps across Android, iOS, Linux, macOS, and Windows, including certificate generation and config. USE WHEN preparing a Tauri build for distribution, setting up signing certificates or keystores, notarizing for macOS, or resolving SmartScreen and Play Store signing requirements.
- ▌ Spark Optimization · sheshiyerOptimize Apache Spark jobs with partitioning, caching, shuffle optimization, and memory tuning. Use when improving Spark performance, debugging slow jobs, or scaling data processing pipelines.
- ▌ Supabase Developer · sheshiyerBuild full-stack applications with Supabase (PostgreSQL, Auth, Storage, Real-time, Edge Functions). Use when implementing authentication, database design with RLS, file storage, real-time features, or serverless functions.
- ▌ Tauri Orchestrator · sheshiyerRoute a Tauri task to the right skill among 40 Tauri specialists — scaffolding, the security/capability model, IPC and the Rust↔frontend bridge, windows/UI chrome, sidecars, plugins, building, signing, per-platform distribution, debugging, and migration. USE WHEN a user is building, configuring, securing, or shipping a Tauri v2 desktop/mobile app but hasn't named the specific concern.
- ▌ Testing Tauri Apps · sheshiyerTesting strategies for Tauri v2 apps: unit tests with the mock runtime, mocking Tauri APIs, WebDriver E2E tests with Selenium and WebdriverIO, and CI on GitHub Actions. USE WHEN writing unit or integration tests for a Tauri app, mocking IPC commands, setting up E2E browser automation, or wiring Tauri tests into CI.
- ▌ Twitter Automation · sheshiyerAutomate Twitter/X posting, engagement, and user management via the inference.sh CLI (post tweets with media, like, retweet, send DMs, follow users, fetch profiles). USE WHEN posting to Twitter/X, scheduling content, building an engagement or growth bot, or integrating the X API into a workflow.