「readiness」の検索結果

Suede-owned launch-appeal grader for public pages. Grades findability, first-screen clarity, CTA pull, proof quality, design signal, and AI citation readiness. Use when a public page needs a fast A-F visibility grade before or after launch. NOT FOR: the deep nine-lane SEO audit with rewrite fixes (use suede-seo-audit); implementing conversion changes (use suede-site-alchemy); getting cited by AI answer engines (use suede-ai-seo).

日本語の概要は準備中です。原文の説明を表示しています。

Suede AI blunt A-F ship grade for a code change across correctness, security and permissions, data and state, domain truth, UX and release behavior, tests and verification, and deploy readiness, with Instant-F triggers and evidence-based grade caps on auth, payment, migration, and public-API surfaces. Use when asked to grade this, give it a letter, is this an A, how ready is this to ship, or should this merge: when the caller wants the verdict without a findings list. NOT FOR: findings, evidence, and fix briefs (use suede-code-review, or suede-code for findings plus grade); enforcing the verdict in CI (use suede-ci-gate); eval coverage for AI behavior (use suede-ai-eval).

日本語の概要は準備中です。原文の説明を表示しています。

CRE Capital Markets and Debt Maturity suite - 8 specialist skills for maturity diagnostics, refinance proceeds gaps, extensions, workouts, rescue capital, term sheet comparison, CMBS special servicing readiness, lender updates, and recap IC memos.

日本語の概要は準備中です。原文の説明を表示しています。

SEO, AEO (Answer Engine Optimization), and GEO strategy for search engines and AI visibility. Use when working on "SEO audit," "technical SEO," "on-page SEO," "AI search optimization," "AEO," "GEO," "AI visibility," "optimize for ChatGPT," "optimize for Perplexity," "AI Overviews," "answer engine optimization," "generative engine optimization," "AI citations," "featured snippets," "meta tags," "schema markup," "search ranking," "content optimization," "E-E-A-T," "structured data," "search console," "SEO health check," "why am I not ranking," "AI search readiness," "backlink strategy," "link building," "domain authority," "programmatic SEO," "SEO at scale," "template-based SEO," "AEO monitoring," "AI search monitoring," "JSON-LD," "rich snippets," "schema.org," "SERP analysis," "search intent," "site architecture," "information architecture," "URL structure," "internal linking," or "navigation." For keyword research, see keyword-research-and-clustering.

日本語の概要は準備中です。原文の説明を表示しています。

Comprehensive go-to-market strategy and launch execution skill. Use when planning a product launch, feature announcement, market entry, or release strategy. Activates for: go to market, GTM, product launch, launch strategy, launch plan, launch execution, launch marketing, GTM playbook, launch readiness, technical launch, beta launch, early access, waitlist, Product Hunt, feature release, announcement, how do I launch this, launch checklist, we're about to ship, market entry, startup GTM, PLG vs sales-led, GTM motion, launch marketing pack, press outreach, developer product launch.

日本語の概要は準備中です。原文の説明を表示しています。

Full repository maintenance pipeline that orchestrates all project agents in sequence - code review, accessibility, bundle size, security, API stability, test coverage, ecosystem, and release preparation. Acts as a quality gate before publishing or merging major changes. Use when: maintenance, health check, pre-release audit, quality gate, full pipeline, repo health, pre-merge check, release readiness, audit all.

日本語の概要は準備中です。原文の説明を表示しています。

Build and verify a HyperGrok trading desk from the pinned public release. Use for first-run setup, repair, or a readiness check. Starts with a live zero-key Opening Bell, installs the seven role profiles and seventeen shared skills, prepares the Trading Floor, and returns an evidence receipt. Read-only by default; never requests a wallet or places an order.

日本語の概要は準備中です。原文の説明を表示しています。

Use when optimizing, auditing, or preparing to ship web animations or rendering performance work: frame loops, scroll/viewport reveals, mount/unmount transitions, canvas/WebGL lifecycles, reduced motion, lazy rendering, and deferred off-screen work. Use for jank, per-frame allocations, forced reflows, render loops, animations that do not pause off-screen, content-visibility, requestIdleCallback, analyzing Chrome DevTools performance traces for animation or rendering issues, or choosing between browser-driven CSS/WAAPI, minimal JS, phase, and Motion/GSAP. Use when the user explicitly asks about phase APIs or behavior. Do not use during exploratory animation ideation, prototyping, visual iteration, or trying variants, even when the code already imports phase; wait until the user asks for performance guidance, an audit, production implementation, ship-readiness review, or about phase itself.

日本語の概要は準備中です。原文の説明を表示しています。

Designs or reviews logs, metrics, traces, alerts, correlation, dashboards, and diagnostic instrumentation so failures and performance changes can be detected and explained at component boundaries. Use for observability work, incident readiness, instrumentation, or production diagnostics. Not for fixing a specific incident before reproducing it or for adding noisy logging without an operational question.

日本語の概要は準備中です。原文の説明を表示しています。

Prepares and controls software releases with risk classification, CI quality gates, artifact provenance, feature flags, staged rollout, measurable promotion and rollback thresholds, post-deploy verification, and cleanup. Use for deployment pipelines, launch readiness, canaries, production rollout, release automation, or rollback planning. Not for merely merging a completed development branch or proving one local change.

日本語の概要は準備中です。原文の説明を表示しています。

Verifies a completion, fix, passing, compatibility, release, or readiness claim with fresh task-specific evidence mapped to the actual requirements. Use before saying a change is done, before merge, after review fixes, and at release gates. Not a substitute for diagnosing the cause of a failing check.

日本語の概要は準備中です。原文の説明を表示しています。

Validates a UX spec, HUD design, or interaction pattern library for completeness, accessibility compliance, GDD alignment, and implementation readiness. Produces APPROVED / NEEDS REVISION / MAJOR REVISION NEEDED verdict with specific gaps.

日本語の概要は準備中です。原文の説明を表示しています。

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is story X ready to implement'.

日本語の概要は準備中です。原文の説明を表示しています。

Read a story file and implement it. Loads the full context (story, GDD requirement, ADR guidelines, control manifest), routes to the right programmer agent for the system and engine, implements the code and test, and confirms each acceptance criterion. The core implementation skill — run after /story-readiness, before /code-review and /story-done.

日本語の概要は準備中です。原文の説明を表示しています。

Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Generates a comprehensive milestone progress review including feature completeness, quality metrics, risk assessment, and go/no-go recommendation. Use at milestone checkpoints or when evaluating readiness for a milestone deadline.

日本語の概要は準備中です。原文の説明を表示しています。

Complete launch readiness validation covering every department: code, content, store, marketing, community, infrastructure, legal, and go/no-go sign-offs.

日本語の概要は準備中です。原文の説明を表示しています。

Validate readiness to advance between development phases. Produces a PASS/CONCERNS/FAIL verdict with specific blockers and required artifacts. Use when user says 'are we ready to move to X', 'can we advance to production', 'check if we can start the next phase', 'pass the gate'.

日本語の概要は準備中です。原文の説明を表示しています。

Smart Contract Systems Architect: Contract system design: modules, upgradeability, access control, storage, audit readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Select and configure a structured discussion protocol matched to the purpose, topic, and group readiness. Use when planning classroom discussions, Socratic seminars, or structured debate.

日本語の概要は準備中です。原文の説明を表示しています。

Medium-native long-form research, author-assistance, writing, editing, review, topic discovery, publication matching, and packaging workflow. Use when creating, outlining, researching, revising, auditing, or packaging Medium stories, essays, tutorials, reviews, explainers, comparisons, case studies, publication submissions, Medium 长文, Medium 选题, Medium Topics, or Medium publishing packs that need original author perspective, narrative craft, relevant topics, responsible AI disclosure, and reader-centered distribution readiness.

日本語の概要は準備中です。原文の説明を表示しています。

Apply evidence-first engineering discipline to any agent-built software project: fact discovery before action, evidence-calibrated status reporting, explicit change boundaries and stage gates, controlled confirmation for risky or external actions, sensitive-information redaction for anything shared publicly, and resumable continuity after interruptions. Use when users ask an agent to take over an existing codebase, deliver a feature across stages, verify whether work is actually complete, judge release readiness, or keep conclusions honest about what is proven versus assumed. This foundation skill is domain-neutral; vertical suites (for example mini-program engineering) build on it by adding domain facts and platform rules.

日本語の概要は準備中です。原文の説明を表示しています。

Analyze WeChat Mini Program platform constraints and evidence layers for an idea or existing repository, including source configuration, build output, WeChat DevTools loading, device behavior, permissions, privacy declarations, cloud or backend linkage, upload, trial, review, and production status. Use when users ask about WeChat-specific configuration, project roots, compile paths, capability permissions, privacy compliance, official platform rules, upload or release readiness, or why source and platform behavior differ. Performs read-only evidence classification by default, verifies time-sensitive or high-risk claims against current official WeChat sources, redacts identifiers and secrets, and never upgrades one evidence layer into another.

日本語の概要は準備中です。原文の説明を表示しています。

Verify mini-program implementations and fixes with risk-calibrated evidence across static checks, unit tests, integration tests, state matrices, simulators, real devices, cloud environments, and release artifacts. Use when users ask to test, validate, accept, regression-check, quality-check, confirm readiness, or determine whether a mini-program feature is actually complete. Binds results to a source and build fingerprint, records commands and observable evidence, separates passed, failed, blocked, and not-run layers, prioritizes the next highest-information check, and never converts local success into device, cloud, release, or formal acceptance claims.

日本語の概要は準備中です。原文の説明を表示しています。