Explore skills
Showing 31711–31740 of 77079 skills
Take a Cogni node from not-deployed to live-and-validated on candidate-a, as a node-contributor agent: get the developer role (env_manager also works), declare the workload, call POST /api/v1/deploy/workloads with env=candidate-a, prove the served build. Use when asked to 'get my node onto candidate-a', 'deploy node X to candidate-a', 'prove a node deploys e2e'. node-setup births the node first. validate-candidate posts the proof.
cogni-dao/cogni
Stars: 4Claude CodeCodexUse when designing, debugging, or operating the Cogni node formation wizard, node formation PRs, submodule-pinned node repos, child image builds, node deploy calls, or AI-assistant launch handoffs. Route launch execution and E2E proof to node-wizard-scorecard.
cogni-dao/cogni
Stars: 4Claude CodeCodexUse when an agent receives a Cogni node wizard launch pack, takes over a newly published throwaway node, or must prove the node-wizard launch path end-to-end across child customization PR, child CI/image, parent pin, operator flight request, and candidate /version verification.
cogni-dao/cogni
Stars: 4Claude CodeCodexThe standard for adding observability to a Cogni node's code — what to log, the event registry, nodeId, metric labels, privacy, and the pre-ship self-check. Use whenever you add or review a route / feature / adapter and must instrument it (logs or metrics) before shipping, or when asked "how do I add proper observability / logging / metrics here", "is this instrumented right", or "review the observability on this PR". The contract lives in the operator knowledge hub, not in this file.
cogni-dao/cogni
Stars: 4Claude CodeCodexUse whenever working on Cogni USDC credit top-ups, payment intent creation, payment activation, operator wallet funding, 0xSplits allocations, x402 outbound provider payments, Hyperbolic, EIP-3009 signatures, retired OpenRouter/Coinbase top-ups, system-tenant revenue share, repo-spec payment config, live payment rail guards, payment CI failures, or debugging money-loop behavior. Trigger on phrases like payments, payment rail, credits top-up, USDC, Split, 0xSplits, splitHash, x402, Hyperbolic, facilitator, signX402Payment, EIP-3009, OpenRouter funding, Coinbase Commerce, operator wallet, Privy wallet, markup_factor, revenue_share, system bonus, provider top-up, settlement_skipped, SPLIT_CONFIG_MISMATCH, activate payments, node payments, or "is this payment behavior validated". This skill is the launching point for future payments work and debugging.
cogni-dao/cogni
Stars: 4Claude CodeCodexPromote a sha to preview or production in cogni-template, OR diagnose why a promotion silently failed. Use this skill whenever the user says "/promote", "promote to preview", "promote to production", "ship to prod", "flight this sha", "deploy this PR to preview", "heal preview", "heal preview-operator", "prod is stuck on the old sha", or asks about preview/prod buildSha not advancing. Encodes the operator-API flight/promote endpoints (promotion runs as the operator, never a personal gh credential), lease semantics, affected-only + admin-merge gotchas (bug.0443), and the Monitor poll-loop you must arm so the dispatch isn't fire-and-forget. Trigger this even when the user only names the symptom ("preview is on stale sha", "production didn't update", "flight-preview hard-failed") — the diagnosis playbook lives here. Do NOT trigger for ordinary code/test/build work; this is exclusively for cd-pipeline operations.
cogni-dao/cogni
Stars: 4Claude CodeCodexProvision (or reprovision) a full environment — candidate-*, preview, or production — via the runner-owned `provision-env.yml` workflow. Covers the before (prereqs + minting secrets), the dispatch, the phase map, the hard-won gotchas that turn a "green" provision into a silent half-deploy, and the after (verify + decommission). Use when standing up a new env, reprovisioning a dead one, debugging a provision that "succeeded" but isn't serving, or when someone says "provision prod / candidate-b", "the new VM isn't up", "ImagePullBackOff after provision", "apex cut over to an empty VM", "525 after provision", "operator pod won't start". Sibling to `https://cognidao.org/knowledge/fork-quickstart-guide` (the forker's zero-to-green) — this is the operator's reference for ANY env on the hub.
cogni-dao/cogni
Stars: 4Claude CodeCodexUse any time you are about to add, change, or migrate a Postgres or Doltgres table — editing schema TS, running `pnpm db:generate:*`, writing a migration `.sql`, touching `meta/_journal.json` / `*_snapshot.json`, or debugging a migration that didn't apply on candidate-a. Mandatory before any schema edit.
cogni-dao/cogni
Stars: 4Claude CodeCodex3rd party API integration expert for cogni-template nodes. Use this skill whenever a node needs to connect to an external API, add a 3rd party service, wrap an SDK, handle webhooks, or design an adapter. Routes the decision between MCP, App Capability, and Port/Adapter patterns using a structured decision matrix grounded in the repo's hexagonal architecture. Enforces top-0.1% standards: Zod-first contracts, typed error hierarchies, pinned API versions, graceful degradation, structured observability, and CI isolation via fake adapters. Trigger this skill at the start of any integration work — before writing any client code — including when someone says "add Stripe", "integrate GitHub", "connect to a webhook", "wrap this API", or "which pattern should I use for this 3rd party service".
cogni-dao/cogni
Stars: 4Claude CodeCodexUI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn/ui MCP for component search and examples.
cogni-dao/cogni
Stars: 4Claude CodeCodexOptionally checks, then commits code to the current or a new feature branch.
Consensys-Incorporated/ocap-kernel
Stars: 10Claude CodeCodexdamus-io/notedeck
Stars: 318Claude CodeCodexCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
jaem1n207/synchronize-tab-scrolling
Stars: 18Claude CodeCodexGitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts. Use when setting up CI build pipelines or downloading GitHub Actions artifacts via gh CLI and GitHub API.
jaem1n207/synchronize-tab-scrolling
Stars: 18Claude CodeCodexAssists with configuring and using Vite as a frontend build tool for modern web applications. Use when setting up dev servers, optimizing production builds, configuring plugins, migrating from Webpack or CRA, or building component libraries. Trigger words: vite, build tool, HMR, hot module replacement, vite config, rollup, bundling.
jaem1n207/synchronize-tab-scrolling
Stars: 18Claude CodeCodexAssists with unit and integration testing using Vitest, a Vite-native test runner. Use when writing tests, configuring mocks, setting up coverage, or migrating from Jest. Trigger words: vitest, unit testing, test runner, vi.fn, vi.mock, test coverage, jest replacement.
jaem1n207/synchronize-tab-scrolling
Stars: 18Claude CodeCodexAfter pushing code or creating a PR, automatically wait for CI checks to complete, fix failures, address Bugbot findings, and re-push in a loop until the PR is green. Use when the user pushes to a PR, creates a PR, or asks to get a PR to green.
Unique-AG/ai
Stars: 5Claude CodeCodexRust/Tauri patterns and best practices for Agentrium backend
talayash/agentrium
Stars: 49Claude CodeCodexSecurity audit checklist and patterns for Tauri desktop apps with PTY spawning
talayash/agentrium
Stars: 49Claude CodeCodexTest-Driven Development workflow with RED-GREEN-REFACTOR cycle and git checkpoints
talayash/agentrium
Stars: 49Claude CodeCodexUse when working with HTTPie (http/https CLI) — the command-line HTTP client for the API era. Covers request items syntax (headers, params, data fields, file uploads), authentication (basic, digest, bearer, plugins), session management, output formatting and printing, SSL/TLS configuration, download mode, configuration files, environment variables, plugin system, exit codes, scripting, and URL syntax. Triggers on: "httpie", "http command", "https command", "http --json", "http --form", "http --download", "http --session", "http --auth", "http --auth-type", "http --print", "http --verbose", "http --follow", "http --offline", "http --check-status", "http --proxy", "http --ssl", "http --cert", "http --verify", "http --format-options", "http --pretty", "http --style", "http --stream", "http --boundary", "http --multipart", "http --raw", "httpie config", "HTTPIE_CONFIG_DIR", "httpie cli plugins", "request items", "data fields", "URL parameters", "HTTP headers", "raw JSON fields", "file upload fields", "named session", "anonymous session", "read-only session", "Content-Disposition", "httpie-unixsocket", "httpie plugins", "AuthPlugin", "TransportPlugin", "ConverterPlugin", "FormatterPlugin".
carapace-sh/carapace-bin
Stars: 2kClaude CodeCodexAnalyze a GitHub issue and create a detailed technical specification
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodexUse when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodexApply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodexApply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodexAnalyze a GitHub issue and create a detailed technical specification
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodexUse when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodexAnalyze a GitHub issue and create a detailed technical specification
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodexUse when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodexApply writing rules to any documentation that humans will read. Makes your writing clearer, stronger, and more professional.
NeoLabHQ/context-engineering-kit
Stars: 1.8kClaude CodeCodex