844건 · 관련도순
Build and debug the shared foundations of DOCA applications on BlueField or ConnectX hardware. Get guidance on device capabilities, memory buffers, context lifecycles, task completion processing, and separate logging controls for the SDK and application.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Capture and decode execution traces from BlueField DPA workloads to inspect kernel events, synchronization, and communication timing. Choose capture modes, adjust file limits and recording overhead, and diagnose empty traces or decoding failures.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Rigorous, defensible email-spoofability verdict and SPF supply-chain risk analysis computed from published DNS alone. Deepens the record-level SPF/DMARC/DKIM/BIMI/MTA-STS/DNSSEC fetch recipes in the offensive-osint arsenal (§16.14) with the reasoning that section doesn't do: a priority-ordered composite verdict for whether an attacker can actually land header-From-spoofed mail in an inbox, and by which vector (exact-domain vs subdomain) — grounded in the single most-misunderstood distinction in email security: the envelope MAIL FROM that SPF authenticates vs the visible header From: that only DMARC governs. Explains precisely why SPF -all/~all alone is NOT spoof-proof without DMARC enforcement, and why SPF +all bypasses DMARC even under p=reject pct=100. Covers RFC 7208 §4.6.4's 10-DNS-lookup / 2-void-lookup PermError fail-open condition with a runnable stdlib-only lookup-counter script, plus the SPF-include-takeover supply-chain vector (an attacker re-registering a dead include inherits SPF-pass authority over the victim domain) with strict transient-vs-NXDOMAIN discrimination discipline so a temporary SERVFAIL is never mistaken for a takeover lead. Fully passive: DNS TXT reads only, no mail sent, no RCPT TO probe, no API keys. Use when auditing a domain's real spoofing resistance (not just its published records), explaining to a client why 'we have SPF -all' does not mean they're covered, investigating an SPF PermError or an unusually long include chain, evaluating a dead SPF include as a takeover lead, or writing a defensible spoofability finding for a deliverable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a multi-quarter roadmap from a backlog of ideas, requests, and ongoing initiatives. Use this skill when planning the next quarter, sequencing dependent work, balancing build vs improve vs maintain, or making the case for what NOT to do. Triggers on roadmap, quarterly planning, what should we build next, sequencing, prioritization, OKR planning, capacity planning, what's on the roadmap, plan the year, what to ship next quarter. Also triggers when stakeholders are pulling in different directions and the team needs a defensible plan.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Translate one internal roadmap into audience-appropriate formats with confidence-band discipline. Use when preparing a roadmap readout, tailoring it for an exec, customer, eng, or sales audience, or auditing over-promise risk.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build a product roadmap with sequenced bets and explicit tradeoffs. Use when asked to "build a roadmap", "prioritize the backlog strategically", "what do we build next quarter", "sequence our bets", "what should we focus on", or "product strategy for the next N months".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Drive the ENTIRE tdmcp roadmap-to-1.0 to completion as a resumable, wave-by-wave campaign — Milestone 4 (generative-AI bridge wave), Milestone 5 (mixer scene arming), and the v1.0 consolidation gates G1–G6 — routing each class of work to the right existing sub-harness. Use whenever the user wants to "implement everything / all the milestones / the whole roadmap / finish the road to 1.0", run the next milestone, close the consolidation gates, or build a long autonomous campaign across M4/M5/G1–G6. ALSO use for every follow-up: continue/resume the roadmap campaign, run the next wave, re-run a failed wave, fold in QA results, check campaign status, re-prioritize, or scope to one milestone/gate. This is the CAMPAIGN layer ABOVE tdmcp-pipeline / tdmcp-feature-lead / tdmcp-backlog-campaign — it sequences across MULTIPLE sub-harnesses (tools, mixer, coverage, docs, bridge, recipes, submission), which the generic backlog-campaign does not. For a SINGLE feature use tdmcp-pipeline; for one tool-shaped backlog file use tdmcp-backlog-campaign. Simple questions can be answered directly.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build an organic-traffic operating system for any site or app: a multi-phase, resumable engine that plans and ships a BATCH ROADMAP of landing pages (use-cases, playbooks, /for/ pages, roundups) on top of real keyword research, with a persistent phase tracker. Use when the user says 'SEO machine', 'build organic traffic', 'rank on Google', 'we need traffic', 'SEO roadmap', 'batch of pages', 'pages roadmap', or 'build an SEO engine'. Distinct from `seo-audit` (one-off diagnostic) and `seo-content` (single-article writer): this skill owns the multi-page roadmap, run sequencing, page generation, internal linking, and the persistent phase tracker across the whole run. For a single alternatives or vs/comparison page, see /competitor-alternatives; for programmatic SEO templates and content at scale, see /seo-content; for off-page link building, see /off-page-seo. Resumable — every invocation continues the last run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Detect drift in .arkhe/roadmap/ context files and regenerate them from the current codebase state. Scaffolds context directory if missing. Use when user runs /roadmap:refresh, mentions "refresh context", "update context", "init roadmap", "stale context", or "scaffold roadmap".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create or update a strategic project roadmap with major milestones. Generates .unikit/ROADMAP.md — a high-level checklist of project goals. Use when user says "roadmap", "project plan", "milestones", "what to build next", "strategic goals", or wants to see big-picture progress. Also use when the user asks to check which milestones are done or wants to plan the overall project direction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Propose the next dependency-ready sprint from the ALREADY-DECOMPOSED roadmap — standup's active sibling. Reads docs/roadmap-execution-plan.md + the memory backlog, computes per-task readiness from the roadmap's machine-readable status, orders with roadmap-planner's graph engine, and emits a proposed task-set (sprint-plan manifest shape) with per-feature done-criteria, excluding unready tasks and naming their unmet prerequisite. PROPOSES ONLY — the human confirms/edits before /triage routes it (typically to the `power` track). Distinct from `sprint-plan`, which decomposes a fresh vision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when authoring or rewriting a roadmap in agents/roadmaps/ — phases, goal, acceptance criteria, council notes; fires even on 'write a plan for X' / 'draft a roadmap'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when implementing a specific item from .plans/ROADMAP.md, a named roadmap phase, or a user-selected roadmap task in this repository. Guides Codex to scope the item, implement it end to end, verify it, and maintain .plans/DEVIATIONS.md for all plan deviations and deferrals.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when an approved PRD must become an executable roadmap — 'gerar roadmap do PRD', 'quebrar o PRD em épicos e features', 'cadeia de dependências', 'roadmap with dependencies' — Phase/Epic/Feature/Task with explicit dependencies, waves and critical path, validated by a deterministic checker, with an approval gate. Do NOT use for a PRD that is not approved (prd- create/prd-refine first).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
분기 성과와 향후 계획을 파랑, 주황, 크림색의 복고풍 HTML 슬라이드 세 장으로 정리합니다. 표지, 세 가지 중점 과제, 로드맵과 핵심 성과 지표를 담습니다.
Review page landmarks, the named regions screen reader users navigate between. The skill checks semantic HTML elements, a single main content region, and labels for repeated region types, then identifies markup changes and ways to verify them.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a page to ensure it has exactly one main landmark, the region identifying its primary content. Find missing or duplicate main regions and get corrections that give assistive technology users a clear navigation target.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Build a marketing plan matched to a company's budget, team, and stage. Organize acquisition, first use, retention, referrals, and revenue into a 90-day roadmap and 12-month outlook, with owners, metrics, and tools in Notion-ready Markdown.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Support product planning for Auri, a voice assistant combining Alexa and Claude. Covers product vision, the Vitoria Neural persona, AWS architecture, service tiers, a four-phase roadmap, market launch planning, success metrics, and competitive analysis.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Structure a post-acquisition improvement plan linking revenue, cost, and operational initiatives to EBITDA, a profit measure. Produce a roadmap with 100-day priorities, performance targets, responsible owners, and an Excel model showing each initiative’s profit contribution.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Configure email security gateways to detect targeted phishing messages. Set up sender impersonation protection, link checks, isolated attachment analysis, and custom rules, then validate quarantine actions and alerts for suspected attacks.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Prepare a graded Claude Managed Agent for recurring schedules, event triggers, or on-demand use. Validate timing, build deployment request data, optionally include self-evaluation for each run, and document the next steps in a roadmap.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Plan security programs for growing companies by estimating financial risk and prioritizing controls. Produce compliance roadmaps, budget justifications, incident response plans, vendor assessments, and board reports that connect security decisions to business impact.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.