Results for “sam”

Estimate market size using TAM, SAM, and SOM with top-down and bottom-up approaches for market opportunity assessment, investor pitches, or market entry evaluation.

Plan and synthesize product/user research with method rigor: select the right method for the goal, compute defensible sample sizes with confidence labels, and cluster coded observations into insights while flagging single-source anecdotes.

Guides collaborative dialogue to turn ideas into approved designs and specs before any implementation begins.

Guides setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness.

Synthesizes the current conversation and codebase context into a structured PRD and publishes it to the project issue tracker with a triage label.

Triage issues through a state machine driven by triage roles, including gathering context, recommending actions, and applying outcomes.

Produces decision-oriented market research, competitive analysis, investor due diligence, and industry intelligence with source attribution.

Plan, design, and analyze A/B tests and growth experiments, from hypothesis to statistically sound results.

Upgrades outdated Maven dependency versions in AEM Cloud Service pom.xml files, handling both literal <version> and same-pom ${property} shapes.

Generate a structured specification document before writing implementation code, validating scope, drafting specs, and registering them in the project.

Breaks a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices, then publishes them to the project issue tracker.

Builds a throwaway prototype to answer a design question, choosing between a runnable terminal app for logic/state questions or multiple UI variations switchable from one route.

Stress-tests a plan against the project's domain model and documented decisions, sharpening terminology and updating DOMAIN.md and ADRs inline as decisions crystallize.

Layer 0 of the keyword research pipeline. Builds a topic-graph snapshot for the brand's category before any seed work, approximated from Semrush phrase_related + phrase_questions on the category seeds plus the brand's own ranking footprint (domain_organic_unique). Idempotent on brand-config hash; never blocks the pipeline; cheap.

Surveys a codebase as a senior advisor and produces prioritized, self-contained implementation plans for other models or agents to execute, without modifying source code.

Implements multiple design variations directly on the real page of a running app, with a live switcher to toggle between them in the browser, then recommends one and integrates it into the codebase.

Generates high-fidelity UI/UX mockups for mobile and web apps using Atomic Design principles, translating product requirements into design specifications with platform-specific layouts and design tokens.

Breaks a plan, spec, PRD, or conversation into independently-grabbable GitHub issues using tracer-bullet vertical slices, then publishes them as native sub-issues under a parent tracking issue via the gh CLI.

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs.

Master orchestrator for the keyword research pipeline. Chains topic-discovery → seed/modifier ideation → competitor + AI-search gap analysis → question mining → BID method → AIO cannibalization check → adversarial redteam → final ranked queue. Same anti-context-bloat pattern as /blog-pipeline (every layer is an Agent dispatch, never a Skill fork).

Set up and verify a connection to an NI USRP radio (USRP E320, N300, N310, N320, N321, X300, X310, or X410) using Wireless Testbench. Use when connecting a USRP for the first time, configuring radio hardware, troubleshooting connection failures, or verifying a radio setup. Covers host inspection (OS, NIC type/speed/MTU), device discovery (findsdru, probesdru), UHD version checking, programmatic radio configuration, and basebandTransceiver verification. Also use when the user mentions USRP setup, radio not found, connection errors, dropped samples, or network configuration for SDR hardware.

Use when building, refactoring, or documenting Graft apps and proxies, including when asked to create a tool server, API server, dual-protocol server, or MCP-HTTP bridge. Graft's core thesis: define tools once and serve them as both HTTP REST endpoints and MCP tools from the same server, with discovery, docs, and OpenAPI generated automatically. Covers concrete actions such as defining tools and handlers, configuring authentication middleware, setting up HTTP and stdio transports, generating OpenAPI documentation, wrapping existing APIs via proxy mode, and wiring up the full CLI workflow.