Results for “build-id”

Run a structured 5-day process to prototype, test, and validate product ideas with real users. Use when the user mentions "design sprint", "validate in a week", "rapid prototype", "test with users", "de-risk before building", "GV sprint", "prototype testing", or "design workshop". Also trigger when a team needs to make a critical product decision quickly, resolve stakeholder disagreements, or test risky ideas before investing in development. Covers mapping, sketching, deciding, prototyping, and testing. For ongoing experimentation, see lean-startup. For customer job analysis, see jobs-to-be-done.

Parses Software Bill of Materials (SBOM) in CycloneDX and SPDX JSON formats to identify supply chain vulnerabilities by correlating components against the NVD CVE database via the NVD 2.0 API, building dependency graphs, calculating risk scores, and generating compliance reports.

Audits an EXISTING UI/codebase for generic AI patterns and applies targeted craft fixes — layout, interactivity, content, iconography, and code quality — without discarding the project's own identity. Use when a UI looks flat, generic, or "AI-slop" and there is code to improve, not build from scratch. Triggers on: "improve the design", "looks generic", "not polished enough", "redesign this", "elevate the UI", "it looks boring", "make it better looking", "apply taste", "design review". Works with any CSS framework. For designing a NEW project's identity from a brief, use `taste-skill` instead — this skill only upgrades what's already built. Source: github.com/Leonxlnx/taste-skill (redesign-skill), restored to the full checklist + the project-identity rule the earlier port had dropped.

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

Clean and package the project for distribution. Removes __pycache__, .venv, build artifacts, data caches, logs, IDE files, coverage reports, and sanitizes API keys in config. Produces a minimal, ready-to-share codebase. Use when user says 'package', 'clean project', 'clean up', '打包', '清理项目', '清理缓存', 'prepare for distribution', 'remove caches', or wants to deliver a clean copy of the code.

Writes long-form articles for Heath Barnett in the Built GTM voice, formatted for Ghost (the Built GTM newsletter and blog), on the LOCKED 10-step template. Trigger on "write an article about", "long-form piece on", "pull this idea", "draft this idea", "turn this into an article", "write a playbook for", "draft a Lens essay about", "Build Log deep-dive on", "write something for Ghost", "run the article process", or any request for content longer than a LinkedIn post. Will not draft without a specific receipt or claim, and will never invent one.

Query the NHGRI-EBI GWAS Catalog REST API for SNP-trait associations, retrieving variants by rs ID, disease/trait, or gene along with p-values and summary statistics. Use when investigating genome-wide association study hits, mapping a SNP or rsID to traits, building polygenic risk scores, or doing genetic epidemiology lookups. Part of the AlterLab Academic Skills suite.

Use this skill for any creative writing task involving narrative, character, story structure, or franchise development. Triggers: building or tracking characters, designing plots, writing scenes or chapters, organizing a story universe, developing motifs or themes, building a series or franchise bible, tracking character arcs, resolving plot gaps, or any request to write or develop fiction at any scale — from a single moment to a multi-story cluster. This skill operates like a narrative OS: it tracks state, identifies gaps, organizes hierarchy, and generates content that is consistent with the established world.

Build a champion, do not just hope you have one. It identifies who inside the account can sell for you, arms them with the internal-sell narrative and a one-pager they can forward, and plans the multi-thread so the deal does not rest on one person. Built for B2B sales teams, customizable to your CRM and your deal process. Trigger on "who is my champion", "build a champion", "arm my champion", "this deal is single-threaded", "help them sell internally", or any multi-thread or champion-development request.

Analyze and improve the internal link structure of an AEM Edge Delivery Services site by building a link graph from the query index and page content, identifying orphan pages, hub pages, and content silos, and generating specific linking recommendations with suggested anchor text and placement.

Greenfield development path for products, tools, and systems that do not yet exist. G Stack validates the idea before anything is planned or built. Use when starting from zero: no existing codebase, no existing schema, no existing API that this extends. AUTO-FIRE immediately when the user says any of: - "new development", "/new-development [description]" - "I have an idea for [X]", "I want to build [X] from scratch" - "new product", "new tool", "new platform", "new application" - "build [X] — it doesn't exist yet", "start a new project" Do NOT use when an existing codebase already exists for the work — use /full-development for large brownfield work. If unsure: ask "Does any part of this already exist in code?" If yes → /full-development. This is the most token-intensive command. Use it when the investment is justified by the scope of what is being built.

Identify the right tool for a process step. Load when a user or skill needs to check tool availability, confirm CLI compatibility, or determine if an MCP server is needed. Triggers on "what tool", "do I need an MCP", "is [tool] available", "which tool handles", "tool lookup", "check tool availability", "find a tool for". Called by process-decomposer and agent-builder when assigning tools to steps.

Build and run the owner's self-branding system in a structured way across LinkedIn, Substack, dev.to, X, profile rewrites, recurring series, and comment strategy. Use when the owner asks for positioning, a branding plan, profile updates, content drafts, a publishing sequence, comment ideas, or help maintaining a consistent public voice. Optimize for operator credibility: specific experience, defensible numbers, concrete artifacts, and category ownership.

Product orchestrator for Prodig Suites that guides product planning, routes work to specialists, and coordinates execution across the product lifecycle. Use when the user is shaping a digital product, deciding next steps, or needs help choosing the right Prodig specialist or workflow. Triggers: 'prodig', 'digital product', 'product idea', 'product planning', 'which product agent should I use', 'SaaS planning', 'course creation', 'template pack', 'productized service'.

Create focused role prompts for agents in multi-agent topologies. Load when agent-builder needs role prompts for agents, or when a user asks to "create an agent prompt", "write a role prompt", "define agent identity", "write an agent role", "prompt for this agent", "write instructions for this agent", "agent persona". Scope: agent role prompts only (v1). System prompts, task prompts, and skill invocation prompts are future TODOs.

Use before any complex or ambiguous task where the path forward is unclear. For breaking down multi-step problems, choosing between approaches, clarifying vague requirements, identifying hidden assumptions, planning before building, and preventing costly mistakes from starting in the wrong direction. Activate when user says "how should I approach this", "what's the best way to", "I'm not sure how to", or presents a problem without a clear solution.

Systematic methodology for auditing the Hermes Skills Hub (and external sources) to identify gaps, overlaps, redundancies, and conflicts when building a skill library for any project. Covers browsing, targeted searching, cross-referencing with web/GitHub, comparing candidates against existing inventory, verifying install safety, and planning installation order. Use when starting a new project and assembling tools, or when evaluating whether to add external skills beyond what's currently installed.

Turn assumptions, funnel opportunities, and product questions into a prioritised, feasibility-checked experiment backlog. Filters by traffic reality, metric latency, and method feasibility — not just ICE/RICE scoring. Maintains a living portfolio with status (idea → designed → running → readout → archived). Load when the user says "what should we test next", "build an experiment backlog", "prioritise our tests", "where should we experiment", "what's worth testing", or when the experimentation orchestrator routes here.

Build and maintain a structured personal-context portfolio for the project owner — identity, working style, goals, team, decision patterns. Includes both an interview protocol for bootstrapping and observable-signal patterns for incremental refinement. Use to bootstrap an owner profile (interview), to refine an existing profile (target one file), or to incrementally update the profile based on observed patterns from a normal session (the agent watches for signals and proposes additions when evidence accrues).

Anti-slop frontend design skill for building NEW landing pages, portfolios, and UI from a brief. Reads the brief and existing brand context first, infers a design direction from three configurable dials (variance, motion, density), and ships interfaces that don't look templated or default-AI. Use when starting a new page/UI with no existing identity to preserve, or when asked to design something "that doesn't look like every other AI landing page." For auditing and upgrading an EXISTING UI, use `taste-redesign` instead — this skill is for the moment before code exists. Triggers on: "build a landing page", "design a portfolio", "make this not look generic/templated/AI-generated", "anti-slop", starting UI work with a brief but no established identity yet. Also owns component-library selection (which package for toasts, dropdowns, charts, drag-and-drop, state, etc.) — use this instead of hand-rolling a component or guessing at a dependency. Source: github.com/Leonxlnx/taste-skill (taste-skill, the main v2 varian

Research, expand, and cluster keywords for content strategy. Use when planning content topics, building keyword lists, expanding seed keywords, clustering by topic and intent, or mapping keywords to funnel stages. Triggers on "keyword research," "keyword expansion," "keyword clustering," "content topics," "what to write about," "topic ideation," "content planning," "6 circles method," "seed keywords," "keyword difficulty," "search volume," "intent mapping," "pillar content strategy," or "content calendar planning." For SEO optimization and auditing, see seo-and-aeo-strategy.

Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing/SEO/brand-voice tasks or content-strategy for planning tasks.

Deprecated redirect skill that routes legacy 'content creator' requests to the correct specialist. Use when a user invokes 'content creator', asks to write a blog post, article, guide, or brand voice analysis (routes to content-production), or asks to plan content, build a topic cluster, or create a content calendar (routes to content-strategy). Does not handle requests directly — identifies user intent and redirects to content-production for writing/SEO/brand-voice tasks or content-strategy for planning tasks.

Brand-first landing page designer — interviews the user to discover brand identity (adjectives, colors, typography, shape language), then generates and iterates on a polished landing page via Stitch with deployment-ready HTML output. Preferred over frontend-design for standalone landing/marketing pages where the user hasn't established visual direction yet. TRIGGER when: user asks to "create/design/build a landing page", "make a homepage for my project/product/service", "build a marketing page", or wants to promote an app/side project. Especially when they haven't defined brand colors, fonts, or visual style — the guided brand interview is the core value. DO NOT TRIGGER when: user has a specific design mockup to implement, wants a dashboard or app UI, needs component-level frontend work (buttons, forms, navbars), is building a multi-page application, or is restyling an existing page with known design tokens. Use frontend-design for those cases.

Breaks natural-language problem descriptions into sub-tasks suitable for DAG nodes. The entry point of the meta-DAG. Identifies phases, dependencies, parallelization opportunities, and vague/pluripotent nodes that can't yet be specified. Uses domain meta-skills when available. Activate on "decompose task", "break down problem", "plan workflow", "what are the steps", "sub-tasks", "task breakdown". NOT for executing the decomposed tasks (use dag-runtime), building the DAG structure (use dag-planner), or matching skills to nodes (use dag-skills-matcher).

autonomous architecture design and refinement for mermate using iterative copilot guidance, local reasoning, repeated low-cost render validation, and final max-quality render selection. use when building, stress-testing, refining, decomposing, validating, or evolving system architectures from simple ideas, complex problem statements, markdown specifications, mermaid drafts, or ambiguous design notes. especially useful when chatgpt should act like a professional architect that thinks step by step, uses mermate repeatedly, compares intermediate diagrams, and decides when to continue refining versus when to finalize with max mode.

Use when building APIs on Hono (Cloudflare Workers, Bun, Deno, Node), debugging route ordering, wiring middleware, validating with @hono/zod-validator, returning streaming responses, configuring CORS with credentials, handling errors via app.onError, or composing typed RPC clients. Triggers: c.env binding types, c.header + c.redirect interaction, missing await next() bugs, Set-Cookie not attaching to redirect, route-precedence surprises, JWT middleware setup, hono/client typed RPC end-to-end. NOT for Express/Fastify/Koa idioms, tRPC/GraphQL paradigms, or Next.js Route Handlers.

Query the STRING API for protein-protein interactions (59M proteins, 20B interactions across 5000+ species), building interaction networks, discovering functional partners, and running GO/KEGG/Pfam enrichment on protein lists. Use when constructing a protein-protein interaction network, expanding from seed proteins to functional partners, or running PPI-based enrichment for systems biology; for curated metabolic pathway maps and reactions prefer alterlab-kegg, and for protein sequences, annotations, or accession ID mapping prefer alterlab-uniprot instead. Part of the AlterLab Academic Skills suite.

Expert Socratic discovery skill for exploring ideas, architecture decisions, and technical design before writing any code. Use this skill — proactively and always first — when requirements are vague, when the user is debating between technical approaches, when the problem is unclear, or when a design decision could have significant architectural consequences. Triggers on: "should we use X or Y", "help me think through", "I'm not sure how to approach this", "what's the best architecture for", "trade-offs between", "design before I code", "let's think through this", "I have an idea", "how should I structure", "help me design", "I want to build X but not sure how", "what approach would you recommend", "is this the right way to". Produces a validated design doc with 2-3 implementation options, trade-offs, and a recommendation. Always use before planning when the approach is not yet locked.

Generates setup table and page objects for Business Central following singleton pattern. Creates setup tables with single-record pattern, primary key field, setup page with auto-initialization on OnOpenPage, GetRecordOnce codeunit helper for performance, and common setup field patterns (Enable/Disable toggles, Default values, Number Series references, Path fields, User IDs). Handles DrillDownPageID and LookupPageID for seamless navigation. Supports multi-tenant and cloud-ready patterns. Use when creating setup tables, implementing module configuration, adding settings tables, creating admin configuration pages, building extension setup, or implementing singleton setup patterns for Business Central.

Comprehensive sales and revenue operations skill. Use when building a sales team, doing founder-led sales, hiring first sales reps, navigating enterprise deals, implementing product-led sales, designing sales compensation plans, defining ICP, mapping buyer personas, or optimizing the revenue engine (RevOps). Activates for: sales strategy, rev ops, revenue operations, sales enablement, sales compensation, ICP, ideal customer profile, buyer persona, sales process, deal execution, lead scoring, lead routing, lead lifecycle, MQL, SQL, pipeline management, CRM automation, sales qualification, BANT, MEDDIC, founder sales, enterprise sales, product-led sales, startup sales, SDR, AE, quota, ramp, commission plan.

GDPR and CCPA/CPRA privacy compliance audit for codebases. Inventories PII fields (email, phone, SSN, IP, device ID, geolocation, biometrics, behavioral data), maps data collection points (forms, APIs, cookies, analytics, error tracking), audits consent mechanisms (cookie banners, opt-in, pre-checked boxes, consent withdrawal), verifies data subject rights implementation (right to access, erasure, rectification, portability, opt-out, Do Not Sell), traces third-party data sharing (Google Analytics, Facebook Pixel, Stripe, SendGrid, Sentry), and checks data retention policies and automated purging. Use when auditing privacy compliance, building data export or deletion endpoints, reviewing cookie consent, or assessing DSAR readiness.

Writes LinkedIn posts for Heath Barnett in the Built GTM voice. Five post types: Build Log (what I shipped + the receipt + the stack), Lens (GTM opinion — takes a position, no hedging), Scar (a mistake and what it cost), Field (what another operator is shipping), Signal (short forward-looking take). Trigger on "write a post about", "LinkedIn post on", "draft a post", "post idea", "turn this into a LinkedIn post", "help me write something about", or any request to create a LinkedIn post for Heath. Will not generate without a specific receipt or claim — asks for the detail first.

Builds, ships, and debugs native iOS apps: lifecycle, permissions, entitlements, push, widgets, StoreKit, and App Store review. Use when a submission is rejected or a guideline blocks a release; when a permission prompt never appears, or a call fails with a missing-entitlement error; when push, background refresh, or a background upload never runs; when a universal link opens Safari instead of the app; when the app is killed by the watchdog, by jetsam, or with 0xdead10cc, hangs on launch, or crashes only on device; when a widget, Live Activity, or app extension runs out of memory; when purchases, subscriptions, or restore fail; when a privacy manifest, tracking prompt, or data label is required; when layout breaks under Dynamic Type; or when a new iOS release breaks a shipped app. Not for Swift language mechanics (`swift`), IDE, signing and build settings (`xcode`), store listings and submission workflow (`app-store`), or cross-platform apps (`react-native`, `flutter`).

Expert NIST Cybersecurity Framework (CSF) advisor covering CSF 2.0 and CSF 1.1. Use this skill whenever a user asks about NIST CSF, cybersecurity risk management, the six CSF functions (Govern, Identify, Protect, Detect, Respond, Recover), CSF profiles, implementation tiers, gap assessments, organizational profiles, community profiles, CSF core subcategories, informative references, or mapping to other frameworks (NIST SP 800-53, ISO 27001, CIS Controls, COBIT). Also trigger for questions like "how do I implement NIST CSF?", "what does CSF 2.0 change?", "help me build a CSF profile", "how do I assess my cybersecurity posture?", or any request involving organizational cybersecurity risk strategy or framework alignment.