coreyone
- 45 skills
- 0 followers
- 1 repo stars
- last month last updated
- ▌ Swarm Rules · coreyone bundleProvides principles and tactical rules for multi-agent collaboration, task scoping, and file race prevention in swarm execution.
- ▌ UX Discovery Artifacts · coreyoneCreates concise early UX discovery artifacts for PRD development, customer development, new product ideas, feature bets, and redesigns. Use when the user asks to hypothesize an ideal customer profile, generate proto-personas, write customer problem or jobs-to-be-done hypotheses, create journey maps, shape value propositions, or turn product context into design-sprint-style customer insight artifacts for product and engineering teams.
- ▌ Analytics Event Tracking · coreyone bundleTrigger: PostHog event, Segment schema, event properties, user funnel track, track taxonomy. Scope: Product behavioral telemetry, user funnel event models. Boundary: Excludes system performance exceptions.
- ▌ Observability Telemetry · coreyone bundleTrigger: structured logging, tracing, telemetry, SLI metrics, SLO alerts, log formats. Scope: Performance metrics, error tracing, production telemetry. Boundary: Excludes client behavioral product funnels.
- ▌ Developer Web Security · coreyone bundleTrigger: web security, XSS mitigation, secure cookies, CSRF, CSP headers, CORS policies. Scope: Frontend and browser-level security boundaries. Boundary: Excludes operating system file storage permissions.
- ▌ Auth And Identity Rules · coreyone bundleTrigger: OAuth 2.1, JWT session, Secure cookies, Keychain storage, auth flow, user authentication. Scope: User authentication, session storage, authorization boundaries. Boundary: Excludes generic data caching.
- ▌ Developer Web Performance · coreyone bundleTrigger: web performance, slow load, bundle size, lazy loading, LCP, CWV optimization, fetch priority. Scope: Frontend optimization, loading speeds, asset minimization. Boundary: Excludes backend database indexing or visual design systems.
- ▌ API Design Guidelines · coreyone bundleTrigger: REST API, GraphQL schemas, HTTP methods, RFC 7807, endpoint structure, API contracts. Scope: API schema design, error models, request/response structures. Boundary: Excludes client-side visual layouts.
- ▌ Failure States Empty States · coreyone bundleTrigger: empty list state, loader skeleton, error boundary layout, offline indicator, system fallback UI. Scope: UI fallback layouts, skeleton placeholders, client recovery views. Boundary: Excludes server-side API error status coding.
- ▌ Tech Stack Preferences · coreyone bundleTrigger: tech stack, preferred tools, SvelteKit, Bun, Drizzle, Zero Sync, Better Auth, Vite. Scope: Project tooling preferences, framework selections. Boundary: Excludes application logic or visual styling guidelines.
- ▌ Design Forms Wizards Checkout · coreyone bundleTrigger: form inputs, wizards, checkout forms, multistep forms, validation UI, input focus. Scope: User-friendly forms design, input constraints, progressive disclosure. Boundary: Excludes backend database schemas or server-side API validation.
- ▌ Data Persistence Caching · coreyone bundleTrigger: database schema, indexing, cache asidePattern, Redis caching, ORM models, Drizzle schema. Scope: Database query tuning, indexing, and data cache designs. Boundary: Excludes user identity validation.
- ▌ System Architecture Rules · coreyone bundleTrigger: clean architecture, hexagonal architecture, domain model, state machine, boundary decoupling. Scope: Software modular design, dependency boundaries, architectural layering. Boundary: Excludes frontend aesthetic styling.
- ▌ Product Management Press Memo · coreyone bundleTrigger: press release, PM memo, PRD memo, product launch narrative, launch story. Scope: Writing press releases and future launch stories for project alignment. Boundary: Excludes writing functional code or task tracking.
- ▌ Developer Code Review Rules · coreyone bundleReview pull requests or audit repositories for correctness, security, performance, test risk, architecture, dependencies, developer experience, documentation, and grounded product direction. Use for code review, repository audits, evidence-backed findings, false-positive vetting, risk assessment, prioritization, or deciding which improvements should become implementation plans.
- ▌ Developer Development Rules · coreyone bundleDesign and implement clear, modular, resilient software and create executor-grade implementation plans with explicit scope, drift checks, verification gates, tests, STOP conditions, dependencies, and delegated-work review. Use for development, refactoring, architecture, implementation planning, safe migrations, handoffs to another engineer or agent, or verifying delegated code changes.
- ▌ Resiliency Circuit Breakers · coreyone bundleTrigger: circuit breaker, exponential backoff, jitter delay, connection timeout, API retry. Scope: Client request resiliency, API retries, fault isolation. Boundary: Excludes visual state loading skeletons.
- ▌ The Elements Of Style Principles · coreyone bundleTrigger: writing style, copy editing, simple copy, prose check, text clarity. Scope: Writing clear, direct, and concise English copy. Boundary: Excludes code formatting or marketing value propositions.
- ▌ Product Strategy Outcome Vision · coreyoneCreates an outcome-backed product strategy memo from an Ideal Customer Profile markdown file, pasted ICP notes, discovery artifacts, product context, or PRD context. Use when asked to create product strategy, convert an UX Discovery and ICP into strategy, define vision-to-outcome strategy, turn discovery into strategic bets, clarify target customer outcomes, evaluate roadmap strategy, or avoid feature-factory planning.
- ▌ Design Information Architecture Rules · coreyone bundleTrigger: sitemap, navigation, menu structure, wayfinding, labeling, search facets, routing links. Scope: Visual hierarchies, wayfinding, navigation model, sitemaps. Boundary: Excludes backend route handlers or page performance tuning.
- ▌ Developer Eval Driven Development · coreyone bundleBuild and improve AI or probabilistic software through evaluation-driven development. Use for LLM applications, agents, prompts, RAG, tool use, classifiers, model migrations, quality regressions, golden datasets, LLM-as-judge rubrics, benchmarks, or requests to add evals and measurable release gates. Pair with TDD for deterministic code; do not use as the primary guide for ordinary unit testing without model behavior.
- ▌ Developer Test Driven Development · coreyone bundleTrigger: TDD, test first, unit testing, integration tests, mock assertions, test-driven dev. Scope: Writing test assertions before coding features, testing paradigms. Boundary: Excludes UX aesthetics or continuous deployment settings.
- ▌ Marketing Copy Emotion Provoking Action Driven · coreyone bundleTrigger: marketing copy, landing text, CTA labels, value proposition, copywriting copy, conversion copy. Scope: Persuasive copy generation, conversion-focused taglines. Boundary: Excludes technical specifications or backend engineering.
- ▌ Peekaboo · coreyoneTrigger: macOS UI, screen recording, simulator UI, desktop app click, capture screen, system dialog, macOS clipboard, menu bar, drag drop. Scope: Automate macOS GUI applications, drive input events, list windows/spaces, and capture visual state via Peekaboo CLI. Boundary: Excludes pure browser-level automation (use chrome-devtools instead) or headless server tasks.
- ▌ Create Prd · coreyone bundleTrigger: PRD, product requirements, spec, problem framing, project scoping, roadmap. Scope: Creating and updating product requirement documents and framing problem scopes. Boundary: Excludes code implementation, design mocks, or CI/CD config.
- ▌ God Marduk · coreyone bundleTrigger: project task list, task decomposition, phase planning, master orchestration, delivery governance. Scope: Project sequencing, task checklist creation, operating governance. Boundary: Excludes tactical code debugging.
- ▌ Developer SEO · coreyone bundleBuild, audit, debug, and migrate websites for durable organic discovery and reliable use by search engines, LLMs, and browser agents. Use for SEO audits or implementation; new sites, routes, templates, CMSs, catalogs, or content programs; crawling, rendering, indexing, robots, canonicals, redirects, sitemaps, hreflang, structured data, metadata, links, faceted navigation, JavaScript SEO, Core Web Vitals, or migrations; keyword, intent, architecture, content, local, media, or authority work; traffic, ranking, CTR, or indexation losses; AEO, GEO, AI Overviews, AI Mode, ChatGPT search, crawler controls, agent-readable pages, Markdown representations, `Accept: text/markdown` content negotiation, `llms.txt`, WebMCP, or agent interaction design. Trigger whenever code or architecture can materially affect public discoverability or machine usability, even if the user does not say SEO. Do not use for paid-search management alone.
- ▌ Aesthetic Rules · coreyone bundleUse when task matches aesthetic-rules aesthetic guidance for visual systems, style selection, and interface quality.
- ▌ A11Y Debugging · coreyone bundleTrigger: a11y, accessibility, ARIA, screen reader, contrast, keyboard, tap targets, focus. Scope: Audit web interface accessibility compliance (WCAG AA). Boundary: Do not use for general backend logic or CSS styling aesthetics.
- ▌ Design Animation · coreyone bundleDesign, implement, audit, and plan interface animation and motion systems. Use for animation reviews, motion audits, easing and duration decisions, gesture physics, transform origins, reduced-motion behavior, animation performance, SvelteKit or Motion integration, perceptual feel checks, or self-contained animation improvement plans.
- ▌
- ▌ Chrome Devtools · coreyoneTrigger: chrome-devtools, browser automation, headless browser, web scraping, inspect element, chrome debugger, inspect page, network request, console logs. Scope: Interact with and automate headless Chrome via Chrome DevTools Protocol (CDP) for testing, debugging, and scraping. Boundary: Do not use for macOS native desktop GUI automation (use peekaboo instead).
- ▌ Aesthetic Science · coreyone bundleUse when task matches aesthetic-science aesthetic guidance for visual systems, style selection, and interface quality.
- ▌ Commerce UX Rules · coreyone bundleTrigger: shopping cart, checkout conversion, checkout flow, payment trust, pricing layout. Scope: Commerce UX optimization, trust badges, checkout pathways. Boundary: Excludes payment gateway API integrations or backend authentication.
- ▌ Cro Commerce Audit · coreyone bundleTrigger: CRO, conversion optimization, checkout friction, user dropoff audit, funnel dropoff. Scope: Diagnosing and auditing checkout and landing page conversion bottlenecks. Boundary: Excludes direct code edits, styling modifications, or analytics database setup.
- ▌ Design Review Rules · coreyone bundleTrigger: design review, visual audit, layout inspection, QA checks, screenshot analysis. Scope: Performing design system compliance audits and interface QA. Boundary: Excludes functional unit testing or database indexing.
- ▌ Design System Rules · coreyone bundleUse when task matches design-system-rules design guidance for IA, usability, responsiveness, systems, motion, and visual QA.
- ▌ Product Management · coreyone bundleTrigger: PM, product tasks, project planning, backlog priority, user stories, ticket scoping. Scope: Product management, task priorities, requirements scoping. Boundary: Excludes writing raw code or designing page layouts.
- ▌ Michael Bolton Rule · coreyone bundleTrigger: standard work, deming first, feedback loop checks, decision rights, delegation check. Scope: Engineering operating models, team governance, task feedback loops. Boundary: Excludes direct code implementation or design templates.
- ▌ Developer Security · coreyone bundleTrigger: security rules, credential leaks, auth tokens, input sanitization, threat model. Scope: Software security guidelines, threat prevention, secure data handling. Boundary: Excludes client-side web browser vulnerabilities.
- ▌ Improve Codebase · coreyone bundleAudit a repository, vet and prioritize evidence-backed findings, write drift-aware implementation plans, delegate bounded work, and independently verify results. Use when asked to improve, audit, modernize, harden, review, plan fixes for, or systematically reduce risk in a codebase. Use native isolated agents for implementation; use OpenRouter/free only for narrow advisory audit slices under its safety limits.
- ▌ Negotiation Maximizer · coreyone bundleUse when the user wants to negotiate a price, rate, compensation, contract, purchase, hotel, service, vendor deal, discount, upgrade, fee, renewal, refund, or other commercial terms; asks what to say to improve leverage or get a better deal; provides an offer/counteroffer and wants a response; or wants to maximize coupons, direct-booking value, bundles, competing configurations, or all-in economics. Do not trigger for ordinary writing, simple price lookup/comparison, arithmetic, generic persuasion, or conflict mediation without a concrete negotiated outcome.
- ▌ Web Deployment Rules · coreyone bundleTrigger: deployment pipeline, CI CD, Docker builds, DB migrations, expand contract database, Netlify. Scope: Application deployment, multi-stage builds, zero-downtime releases. Boundary: Excludes local editor settings.
- ▌ Design Usability Rules · coreyone bundleUse when task matches design-usability-rules design guidance for IA, usability, responsiveness, systems, motion, and visual QA.
- ▌ Design Responsive Rules · coreyone bundleTrigger: responsive layout, media queries, mobile view, desktop layout, tablet break points, thumb zone. Scope: Multi-device layouts, breakpoints, mobile touch zones. Boundary: Excludes backend API design or database scaling.