1,051 件 ・ 関連度順
概要と使いどころ
Design, refine, implement, or review application UI and user journeys with minimal controls, clear actions, shared components, realistic prototypes, and polished behavior. Use for product screens, forms, onboarding, navigation, settings, and chat/task interfaces; not backend-only work or general graphic design.
日本語の概要は準備中です。原文の説明を表示しています。
Builds vendor-agnostic detection rules using the Sigma rule format for threat detection across SIEM platforms including Splunk, Elastic, and Microsoft Sentinel. Use when creating portable detection logic from threat intelligence, mapping rules to MITRE ATT&CK techniques, or converting community Sigma rules into platform-specific queries using sigmac or pySigma backends.
日本語の概要は準備中です。原文の説明を表示しています。
Install DSH on a fresh Mac. Runs sovereign-setup-mac.sh, renders .env from secrets backend, applies full sovereign lockdown, probes machine, and pulls right-sized Ollama models — one guided flow that leaves the node hardened and ready for Phase-2 spore.sh activation.
日本語の概要は準備中です。原文の説明を表示しています。
After navigating and interacting in Cursor's built-in browser, use browser_network_requests to audit every fetch/XHR for failures, slowness, duplicate calls, and suspicious payloads. Use for API-heavy pages and after backend or client networking changes.
日本語の概要は準備中です。原文の説明を表示しています。
Fast in-memory DataFrame library for datasets that fit in RAM. Use when pandas is too slow but data still fits in memory. Lazy evaluation, parallel execution, Apache Arrow backend. Best for 1-100GB datasets, ETL pipelines, faster pandas replacement. For larger-than-RAM data use dask or vaex.
日本語の概要は準備中です。原文の説明を表示しています。
Design schemas and migrations, tune queries, or plan vector retrieval and database operations. Application API implementation uses oma-backend.
日本語の概要は準備中です。原文の説明を表示しています。
Implement server APIs, authentication, and application data access. Schema modeling and query tuning use oma-db.
日本語の概要は準備中です。原文の説明を表示しています。
Creates TanStack Query hooks for API features with authentication. Use when connecting frontend to backend endpoints, creating data fetching hooks.
日本語の概要は準備中です。原文の説明を表示しています。
バックエンド実装時に使用。DRY原則遵守。コーディング規約準拠。
Provides expert knowledge of Spring Boot conventions, Kotlin idioms, and MVC patterns for backend API development.
日本語の概要は準備中です。原文の説明を表示しています。
Design, implement, and review web interface layout, component states, feedback, and motion within the current CodeConductor workflow. Use for concrete web UI work or requested UI audits, not backend-only tasks or native mobile apps.
日本語の概要は準備中です。原文の説明を表示しています。
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
日本語の概要は準備中です。原文の説明を表示しています。
Provides and generates complete CRUD workflows for Spring Boot 3 services. Creates feature-focused architecture with Spring Data JPA aggregates, repositories, DTOs, controllers, and REST APIs. Validates domain invariants and transaction boundaries. Use when modeling Java backend services, REST API endpoints, database operations, web service patterns, or JPA entities for Spring Boot applications.
日本語の概要は準備中です。原文の説明を表示しています。
Harden iOS/Android apps you ship: storage, TLS pinning policy, IPC, and backend trust. You still enforce authz on the server.
日本語の概要は準備中です。原文の説明を表示しています。
Kotlin/Spring Boot 3.x patterns - use for backend services, REST APIs, dependency injection, controllers, and service layers
日本語の概要は準備中です。原文の説明を表示しています。
Builds reusable Convex components with isolated tables and app-facing APIs. Use for new components, reusable backend modules, integrations, or component boundary work.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize end-to-end application performance with profiling, observability, and backend/frontend tuning. Use when coordinating performance optimization across the stack.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy containerized frontend + backend applications to Azure Container Apps with remote builds, managed identity, and idempotent infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Master proven backend architecture patterns including Clean Architecture, Hexagonal Architecture, and Domain-Driven Design to build maintainable, testable, and scalable systems.
日本語の概要は準備中です。原文の説明を表示しています。
Goal-integrity skill. Use for backend/API/persistence, preserve/do-not-change, tests/validation, mocks, rework, multi-part requests. Emits Goal Contracts, Deviation Notices, Phase Checks, Final Audits. Skip for Q&A or trivial edits.
日本語の概要は準備中です。原文の説明を表示しています。
Deploy web apps with backend APIs, database, and file storage. Use when the user asks to deploy or publish a website or web app and wants a public URL. Uses HTTP API via curl.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a small, well-bounded change done now without a plan file — a bugfix, config change, rename, doc update or simple refactor touching 1–5 files — 'corrigir rapidinho', 'quick fix no X', 'renomear Y'. Presents a mini-plan, implements after approval, verifies and commits. Do NOT use for more than 5 files, architectural decisions, migrations or new UI flows (use feat-feature / feat-backend / feat-frontend).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a UI-only action plan — components, pages, composables/hooks, state, forms and their E2E coverage — 'plano de frontend para a tela X', 'plan the settings page'. Writes .planning/feat/features/{slug}/plan.md with E2E scenarios and playwright-cli checks. Do NOT use for API/database work (feat-backend), full features (feat-feature), writing code (feat-exec) or UI review (feat-review).
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to execute an existing pwdev-feat action plan — 'executar o plano user-crud', 'exec latest', 'rodar o plano', 'retomar a execução'. Dispatches the executor (subagent when the runtime has one, inline otherwise) in IMPLEMENT or REPORT mode, handles NEEDS_ADVICE with the advisor, and supports --resume. Do NOT use to create plans (feat-feature, feat-backend, feat-frontend, feat-test, feat-review) or for tasks without a plan (feat-quick).
日本語の概要は準備中です。原文の説明を表示しています。