「cat」の検索結果

Unify 6+ memory systems into AgentDB with HNSW indexing for 150x-12,500x search improvements. Implements ADR-006 (Unified Memory Service) and ADR-009 (Hybrid Memory Backend).

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

Deep agentic-flow@alpha integration implementing ADR-001. Eliminates 10,000+ duplicate lines by building claude-flow as specialized extension rather than parallel implementation.

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

Master advanced AgentDB features including QUIC synchronization, multi-database management, custom distance metrics, hybrid search, and distributed systems integration. Use when building distributed AI systems, multi-agent coordination, or advanced vector search applications.

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

Urdu-first digital experiences with native RTL support, Nastaliq typography, and bilingual Urdu/Latin harmony. For editorial, personal, and publication layouts.

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

Carefully curated, modern minimal style with elegant serif typography and understated, sophisticated palettes.

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

Print-inspired visual language for books, magazines, and reports with editorial grids and expressive typography.

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

App dashboard with purple-themed aesthetic, top-bar navigation, card-based layouts, and developer-first workflows.

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

Structured, enterprise-focused design system emphasizing clarity, consistency, and efficiency for data-dense web applications.

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

Hand-drawn paper-wireframe template — white paper background, monochromatic ink palette, SVG turbulence "wobble" filters for pen-quiver authenticity, handwritten fonts (Caveat / Kalam / Ma Shan Zheng / Long Cang), wavy dividers, sketch-rect overlays, marginalia annotations. For PRD illustrations, IA flow docs, low-fidelity layout exploration, "draft / not final" stakeholder communication. Three skeletons (single-page editorial / app multi-screen flow / IA sitemap) — pick one up front based on the artifact, do NOT inherit only the brush strokes.

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

Step through versioning, tagging, and verification

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

Definition, documentation, and application of design tokens for Vue 3 + shadcn-vue. Use when configuring a new project, extracting tokens from Figma, or ensuring token consistency across Vue components.

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

Audit of existing Vue components in the project. Use when reviewing Vue design system consistency, identifying duplicate patterns, evaluating legacy components (Options API), or before implementing something new.

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

Independent, traceable code review of one SDD Composy task in review_required against its approved PRD, stories, TechSpec, evidence, and project rules, with stable findings and severities. Use when a task passed QA and evidence — 'revisar a TASK-003', 'code review da task', 'review this task's diff'. Do NOT use for code review outside an SDD workspace (use the host code review), for QA (sdd-qa), or for verification (sdd-verify).

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

Adversarial verification of one SDD Composy task in verify_required: reproduce every claim with fresh commands, build the truth table, refute stale evidence, and produce the verdict that gates complete. Use when review is done and the task claims to be finished — 'verificar a TASK-003', 'a task está pronta mesmo?', 'is this task really complete'. Do NOT use for QA, code review, or a general 'verify my work' outside an SDD task.

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

Run a bounded, provider-neutral SDD Composy correction loop on one approved task (EXECUTE, QA, EVIDENCE, REVIEW, VERIFY; at most 3 iterations) with explicit approval, safe-stop guards, and fresh verification. Use to continue an approved TASK autonomously — 'rodar o loop na TASK-003', 'continuar a task até passar', 'start a loop on task 4'. Do NOT use for the host's recurring loop runner, for fleets (sdd-fleet), or for a task without human approval.

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

Create or revise the SDD Composy technical specification (tasks/prd-SLUG/techspec.md) from the approved PRD, resolved stories, and mapped codebase, with DEC/RISK and TU/TI/E2E traceability and a human gate. Use when the product contracts are approved and architecture is needed — 'criar a spec técnica', 'techspec do prd-SLUG', 'design the solution for…'. Do NOT use to change product scope, before PRD and stories approval, or for design notes outside SDD.

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

Design traceable API checks for contracts, authentication, authorization, errors, and idempotency with observable outcomes.

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

Use when about to claim work is complete, fixed, or passing, and when a finished feature needs adversarial verification before integration

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

Review or refactor an existing SKILL.md and its bundled resources — a smaller always-loaded core, conditional references, preserved behavior, lean/guided consumer profiles, and an A/B protocol to compare a candidate with the previous version. Use when a skill repeats itself, loads references on every run, triggers too broadly or misses legitimate requests, or needs its efficiency measured across models. Do NOT use for writing a new skill from scratch, refactoring application code, translating a skill verbatim, or performing the target skill's own task.

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

Execute approved PWDEV Flow plans one atomic task at a time with test-first implementation, fresh verification, blocker handling, and durable evidence. Use after the plan gate is approved or for approved Flow correction tasks.

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

Deliver a small, bounded code change through inspection, a mini-plan, implementation, testing, review, and adversarial verification. Use for bug fixes, configuration changes, and features expected to touch no more than five files.

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

Design an approval-gated feature specification from approved requirements. Use when PWDEV Flow discovery is complete and the user needs architecture decisions, component boundaries, quality constraints, and a definition of done.

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

Adversarially verify an implementation against its objective, acceptance criteria, definition of done, and prohibitions using fresh evidence. Use for completion gates, release readiness, or independent verification after implementation and review.

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

Design precise, production-grade enterprise UI — dashboards, admin panels, SaaS interfaces, and data-heavy applications. Use this skill for professional software interfaces that need Jony Ive-level craft: clean, minimal, functional, with intentional personality. Do NOT use for creative landing pages, marketing sites, or experimental/artistic frontends.

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