Testing & Security skills

ランタイム、パッケージマネージャー、バンドラー、テストランナーとしてのBun。Bun vs Nodeの選択基準、マイグレーションノート、Vercelサポート。

The English summary is being prepared. Showing the original description.

Djangoプロジェクトの検証ループ：マイグレーション、リンティング、カバレッジ付きテスト、セキュリティスキャン、リリースやPR前のデプロイ準備チェック。

The English summary is being prepared. Showing the original description.

This skill should be used when the user wants to "synthesize two competing solutions without averaging", "resolve a design/value disagreement by lifting to a higher frame", "止揚 / アウフヘーベン", "矛盾を止揚", "独立案を統合", "平均化せず統合", "contradiction lift", "sublate competing designs", or has two good-but-divergent answers to the same question and wants a higher-order resolution (a selection mechanism) or an honest aporia — not a compromise. NOTE: Use this when two independent solutions diverge and you want to PRESERVE both truth-moments while lifting to a higher frame. Use devils-advocate to stress-test ONE proposal with an assigned opponent, strong-inference to find an unknown cause, and dialectic-loop to validate a claim against a real corpus.

The English summary is being prepared. Showing the original description.

This skill should be used when the user wants to "test a claim against data", "validate an empirical hypothesis", "refine a model/theory with evidence", "characterize a pattern and verify it", "演繹と帰納で検証", "仮説をデータで検証して更新", "実例と反例で確かめる", "弁証法ループ", "主張を現物で裏取り", "傾向分析を検証して精緻化", or mentions iteratively updating a hypothesis by deriving predictions and testing them against a real corpus. NOTE: Use this for VALIDATING/REFINING an empirical claim or model against real data through a derive→test→update loop. Use strong-inference for debugging an UNKNOWN cause, and devils-advocate for adversarially stress-testing a DESIGN proposal.

The English summary is being prepared. Showing the original description.

This skill should be used when the user wants to "stress-test a design", "challenge an idea", "red team a proposal", "get critical feedback on a design", "validate a design", "adversarial architecture review", "risk assessment", "設計を検証して", "反論をもらいたい", "設計を批判的にレビュー", "デビルズアドボケート", "ストレステスト", "弱点を指摘して", "穴を見つけて", "この設計で良いか", "リスク評価", "設計のアーキテクチャレビュー", or mentions structured adversarial review of a proposal or design. NOTE: Use this for validating PROPOSALS and DESIGNS through adversarial debate, NOT for generic code review, PR review, or normal review requests (use /codex:review or /codex:adversarial-review for those). Also NOT for investigating unknown bugs (use /agent-dialectics:strong-inference for that).

The English summary is being prepared. Showing the original description.

Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.

The English summary is being prepared. Showing the original description.

Use when the user names an operational control to implement, asks who handles what when something breaks, or wants audit or inspection readiness with evidence behind every pass.

The English summary is being prepared. Showing the original description.

Prepare and execute negotiations using tactical empathy, calibrated questions, and the Ackerman method. Use when the user mentions "salary negotiation", "contract terms", "handling objections", "mirroring and labeling", "difficult conversation", "deal terms", "BATNA", "anchoring", "how do I ask for a raise", "get a better deal", or "they wont budge on price". Also trigger when preparing for a vendor negotiation, resolving a pricing dispute, or navigating a high-stakes conversation where both sides need to feel heard. Covers accusation audits, Black Swan discovery, and the "Thats Right" technique. For persuasion in product and marketing, see influence-psychology.

The English summary is being prepared. Showing the original description.

Audit a page the way a search engine reads it: what it is about, whether that is obvious, and the three fixes worth doing before anything else.

The English summary is being prepared. Showing the original description.

Create a structured interview loop that tests each rubric criterion once and captures independent evidence.

The English summary is being prepared. Showing the original description.

Talk to customers without leading them using Mom Test rules: discuss their life not your idea, ask about specifics in the past, and talk less. Use when the user mentions "customer interviews", "validate my idea", "users say they want it but dont buy", "leading questions", "The Mom Test", "customer feedback bias", or "interview script". Also trigger when preparing user-research questions, interpreting ambiguous feedback, or designing customer-discovery that avoids false positives. Covers commitment and advancement, avoiding compliments, and extracting signal from noise. For product-market fit, see jobs-to-be-done. For rapid prototype testing, see design-sprint.

The English summary is being prepared. Showing the original description.

Discover what customers truly need by analyzing the "job" they hire your product to do. Use when the user mentions "customer discovery", "why customers churn", "what job does this solve", "competing against luck", "product-market fit", "switching behavior", "milkshake moment", or "functional vs emotional jobs". Also trigger when investigating why users choose competitors, designing features around real customer needs, or reframing a value proposition. Covers JTBD interviews, competition analysis, and jobs-oriented roadmaps. For product positioning, see obviously-awesome. For rapid validation, see design-sprint. For non-leading interview technique, see mom-test.

The English summary is being prepared. Showing the original description.

Use when a large deal needs procurement, legal, security, and pricing orchestration: mutual close plans, deal-desk runs, and signature.

The English summary is being prepared. Showing the original description.

Triage an intermittent test from run history, environment, and failure pattern before naming a cause.

The English summary is being prepared. Showing the original description.

Audit CRM fields by fill rate, format, and use, and propose keep, fix, or retire for each.

The English summary is being prepared. Showing the original description.

When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.

The English summary is being prepared. Showing the original description.

Prepare a neutral brief for counsel or the security lead on a matter that needs their judgement.

The English summary is being prepared. Showing the original description.

Track compliance requirements and audit readiness. Trigger with "compliance", "audit prep", "SOC 2", "ISO 27001", "GDPR", "regulatory requirement", or when the user needs help tracking, preparing for, or documenting compliance activities.

The English summary is being prepared. Showing the original description.

Use when deals must clear compliance gates: licensing, suitability, audit readiness, and regulated-ops checks before close.

The English summary is being prepared. Showing the original description.

Set up compliance work from policies, system inventory, audit reports, approved answers, and counsel contacts.

The English summary is being prepared. Showing the original description.

Read an ad test by sample size and spread, and say whether there is a winner yet.

The English summary is being prepared. Showing the original description.

Review a deal for evidence gaps across need, scope, stakeholders, process, competition, delivery, security, legal, and commercial approval.

The English summary is being prepared. Showing the original description.

Review a dependency change for breaking APIs, runtime shifts, supply-chain risk, test gaps, rollout risk, and rollback quality.

The English summary is being prepared. Showing the original description.

Set up dependency and security hygiene from repository evidence, with a clear scope, source list, risk queue, and approval line.

The English summary is being prepared. Showing the original description.