'specs' 검색 결과

Create UTM links, which identify traffic sources, and GA4 event specifications for marketing campaigns. Standardize names across advertising and email channels, with platform-specific parameter templates, implementation notes, and recommendations for checking tracking before launch.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Create tracking links for campaigns across multiple channels
• Standardize campaign naming rules across a team
• Define GA4 events for purchases and form submissions

Inventory old and undocumented API versions, then compare their authentication, request limits, input validation, and exposed fields with current versions. Uses API specifications and archived records to identify overlooked endpoints with weaker security controls.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding API versions left reachable after deprecation
• Comparing old and current OpenAPI or Swagger specifications
• Checking security differences between API versions

Expose new backend API endpoints through the TypeScript SDK, or record intentional exclusions. Follow existing entity and client conventions, check generated request types, and verify that each endpoint is either used by the SDK or explicitly skipped.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding SDK support for a new Rust service endpoint
• Investigating endpoints reported as uncovered
• Recording agreed SDK exclusions

Create code documentation, API specifications, documentation sites, and developer guides. Adapt formats to the language and framework, explain parameters and errors, test documentation examples, and report which public functions and classes have been documented.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding docstrings and JSDoc to code
• Creating OpenAPI specifications and API portals
• Building documentation sites

Guide implementation, upgrades, and debugging by checking official documentation and local specifications first. Identify the relevant version, confirm supported behavior, and use those findings to produce an implementation or answer with appropriate validation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Integrate an external API using official documentation
• Check breaking changes before upgrading a library
• Investigate errors caused by API changes

Rebuild an app’s visual system as reusable design values and component specifications. It covers typography, spacing, component states, implementation, and contrast checks while replacing the original app’s branded assets with independent alternatives.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reconstructing design rules from app screenshots
• Defining shared tokens and component states
• Checking text and background contrast

Turn Figma screens and components into code that follows an existing project's conventions. The workflow retrieves design details and assets, reuses existing components, and checks the resulting interface against Figma screenshots.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Implementing a button from a Figma design
• Building a dashboard from a Figma frame
• Extending existing components to match a design

Turn documentation, code, and specifications into reusable Agent Skills. Define when each skill should activate, organize supporting references, add reproducible examples, and check new or existing skills with templates, a checklist, and a validator.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an Agent Skill from documentation and code
• Reorganizing an overly long SKILL.md
• Clarifying skill activation conditions and boundaries

Review specification files to see the current phase, completion levels, and remaining tasks. Get a progress report that identifies next steps, blockers, dependencies, and related specifications that may need checking after changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check a specification’s progress and remaining tasks
• Identify next steps and blockers
• Review related work that may need checking after changes

Turn pending roadmap features into requirements, technical designs, and implementation tasks. Independent features run in parallel, while prerequisite features finish first. A final review checks shared data, interfaces, naming, and responsibility boundaries across specifications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generate specifications for multiple roadmap features
• Plan specifications around feature dependencies
• Check shared data and interfaces across specifications

Review a completed implementation task against approved requirements, design, and assigned scope. The skill inspects code changes and verification evidence, checks tests and hidden dependencies, and returns an approval or rejection with specific findings and required fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reviewing a task after implementation
• Rechecking fixes after a rejected review
• Checking for changes outside the approved task scope

Generate requirements, technical designs, and implementation tasks for pending roadmap features in Cascade. Features are processed one at a time in dependency order, followed by a review of consistency and responsibility boundaries across specifications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Generate specifications for multiple features in Cascade
• Process feature specifications in dependency order
• Check shared data and interfaces across specifications

Create requirements, designs, and task lists for multiple roadmap features in dependency order. Independent features run in parallel when supported, followed by checks that shared data, interfaces, naming, and work boundaries agree across specifications.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Prepare specifications for multiple planned features
• Sequence specification work by feature dependencies
• Check shared data and interfaces across specifications

Refresh a LinkedIn profile for a job search from the user's own resume — pick and check the profile photo, crop it locally to LinkedIn, Slack and GitHub sizes, and write a headline and About section grounded in the resume, then check that LinkedIn, GitHub and the resume tell the same story. Use when the user asks to "update my LinkedIn", "write my LinkedIn headline/About", "is this a good LinkedIn photo", "resize my headshot for LinkedIn", or shares a resume or profile photo for job-search feedback. Uses the free ProfessionalHeadshot.io MCP for official photo specs and photo scores when connected; works without it.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Scan a repo for mixed ADRs, PRDs, SPECs, and DOCs and bootstrap or merge the full .planning/ setup from them. Classifies each doc in parallel, synthesizes a consolidated context with a conflicts report, and routes to new-project or merge-milestone depending on whether .planning/ already exists.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

[omh] Deep dive before a decision: deep research engine - grounding for specs and decisions: study open-source reference implementations with pinned refs, gather live web evidence with citation discipline, verify contested claims, and distill a decision-grounding dossier that planning consumes; for a decision brief use research-brief, for upstream guidance use web-research. Use when the user says: research plan, literature review, research literature, review recent papers, deep research, deep-research, exhaustive research, saturation research.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Explore and understand codebases using SocratiCode semantic search, dependency graphs, and context artifacts. Use when exploring code, understanding architecture, finding functions/types, analysing dependencies, searching database schemas or API specs, or when socraticode/codebase_search tools are available. Activates when the user asks about code structure, wants to find where a feature lives, or needs to understand how code is organised.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when code changes may have made documentation outdated, when reviewing docs for consistency, or when the user asks to sync or audit documentation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Calculate contract-based futures position sizes from a direction, entry, and stop-loss, using verified per-symbol contract specs (multiplier, tick size, tick value). Use when the user asks how many futures contracts to trade, wants to size a futures position (ES, NQ, ZB, GC, CL, 6E/E6, VX, BT, ...), or is handing off a contrarian-setup-gate READY_FOR_PLAN direction/invalidation_level for sizing. Pure, offline calculation -- no API keys, no network.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate and prioritize US equity long-side edge research tickets from EOD observations, then export pipeline-ready candidate specs for trade-strategy-pipeline Phase I. Use when users ask to turn hypotheses/anomalies into reproducible research tickets, convert validated ideas into `strategy.yaml` + `metadata.json`, or preflight-check interface compatibility (`edge-finder-candidate/v1`) before running pipeline backtests.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "build the norm card for this platform", "what are the char limits and visible-fold cutoffs here", "is the LinkedIn link-in-first-comment thing documented or folklore", or "which of our platform cards are stale"; maintains the dated, versioned per-platform norm cards in the references/platforms/ pack — char limits, visible-fold cutoffs, hashtag norms, format/aspect specs, link and first-comment placement, disclosure-label mechanics, algorithm emphases (e.g. 小红书 search+saves weighting) — every row labeled platform-documented (official doc, Measured) or Estimated-folklore (named source) with last-verified and review-by dates, and any card past its review date flagged stale rather than trusted. Extends the single pack in place; never forks a second one. Not for picking which channels to run — use channel-portfolio-planner. 平台规范卡/字符限制/折叠线/话题标签/算法侧重/过期标记

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user asks to "package the launch assets", "build a press kit", or "prep the store listing and go-live checklist"; produces a tier-scoped launch asset manifest with production status — a press kit spec (factsheet, description, history, features, videos, images, logo and icon, awards, contact), demo script and screenshot specs, a launch FAQ, dual-store listing metadata drafts against the official character budgets (per App Store Connect / Play Console documentation), and a technical go-live checklist manifest (robots flip, sitemap, OG tags, analytics verification — execution stays with technical-seo-checker and serp-markup-builder). Not for the message copy itself — use message-house-builder or content-writer; not for landing page UX — use landing-optimizer; not for keyword research beyond the store surfaces — use keyword-research. 发布资产打包/press kit/商店listing规格/上线检查清单

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.