「stack」の検索結果

Multi-cycle diagnostic pipeline: profile → research → optimize → repeat with full-stack bottleneck analysis

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

Universal platform artifact cleaner: Replit, StackBlitz, CodeSandbox, Glitch

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

Audits project physical structure: file hygiene, ignore file quality, framework convention compliance, domain/layer organization, naming conventions. Stack-adaptive via auto-detection.

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

Creates 4 core project docs (requirements.md, architecture.md, tech_stack.md, patterns_catalog.md). ALWAYS created.

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

Creates reference documentation structure + smart documents (ADRs/Guides/Manuals) based on TECH_STACK. Only creates justified documents (nontrivial technology choices).

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

Audits env var config: file inventory, code-to-example sync, default desync, naming, startup validation. Stack-adaptive.

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

Analyzes application logs: classifies errors, checks log quality/format, maps stack traces to source, recommends fixes.

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

Master index for DecisionsAI harness setup — ECC, Ponytail, Fallow, RTK, browser/content skills, and IDE thread tools.

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

Index of DecisionsAI browser automation, computer-use, browser QA, and workflow integration across Codex, Cursor, Claude, and Pi.

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

Audit your company's AI spending — find waste, measure ROI, and right-size your tool stack.

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

Full-stack affiliate marketing automation for OpenClaw agents. Generate, track, and optimize affiliate links with FTC-compliant disclosures and multi-network support.

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

Deploy smart contracts and bridge assets to Abstract (ZK Stack L2). Use when an agent needs to deploy contracts on Abstract, bridge ETH/tokens to Abstract, trade/swap tokens, check balances, transfer assets, or interact with Abstract mainnet. Covers zksolc compilation, Hardhat deployment, Relay bridging, DEX trading, and key contract addresses.

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

Deploy smart contracts and bridge assets to Abstract (ZK Stack L2). Use when an agent needs to deploy contracts on Abstract, bridge ETH/tokens to Abstract, trade/swap tokens, place predictions on Myriad Markets, check balances, transfer assets, or interact with Abstract mainnet. Covers zksolc compilation, Hardhat deployment, Relay bridging, DEX trading (Kona, Aborean), Myriad prediction markets, and key contract addresses.

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

Use when building a frontend and the user wants a distinctive / animated / "wow" UI element in React + Tailwind - e.g. a laptop-opening-on-scroll, 3D tilt card, spotlight hero, animated beams/background, marquee, bento grid, interactive globe, meteor/particle background, shimmer button, or scroll/reveal motion. Fetches the showpiece component LIVE at build time from code libraries (Aceternity, Magic UI, Cult UI, ReactBits, 21st.dev) via their shadcn registry command (or WebFetch fallback), then adapts it to brand tokens. Also covers plain components (button, form, modal, table, etc.) as a fallback. Triggers on "make it pop", "something flashy", "animated [X]", "like [cool site]", "build a [showpiece] section". NOT for non-React stacks. Inspiration galleries (Dribbble/godly) are visual reference only - never code.

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

Cross-stack security review — auditing vulnerabilities across infrastructure, smart contracts, CI/CD pipelines, and AI agent systems, plus auth/sessions/crypto and validating user input at API and infrastructure boundaries. Triggers on mentions of "vulnerability", "pentest", "OWASP", "access control", "injection", "CSRF", "JWT", "smart contract audit", "supply chain", "OIDC", or any review of security-sensitive code paths spanning more than one layer. For PII sanitization see [security](../security/SKILL.md).

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

Implement or review dygo Studio behavior in Vue, TypeScript, Pinia, TanStack Query, Vue Router, the dygo design system, and framework renderers. Use for Studio application logic, navigation, state, API integration, and shared components.

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

This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React Router).

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

Diagnose Sentry issues without copy-pasting stack traces. Uses the Composio CLI to pull issue details, events, breadcrumbs, and suspect commits, then maps the frames to local source so the agent can propose a fix directly.

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

Validate the GenAI stack (services, authentication, models, notebooks, GPU). Arguments: [all|services|auth|models|notebooks|vram] [--full] [--auth-only] [--nodes-only] [--notebooks]

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

Auto-activate for msgspec, Struct, Meta, msgspec.json, msgspec.msgpack, tagged unions, enc_hook, dec_hook, convert(), or Litestar DTO shapes. Not for Pydantic or ORM models — use their stack-specific skill.

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

Security launch audit for a public web app BEFORE you ship or hand it to a client — "vibe coders are getting sued", systematized. An executable pipeline: classify (static / full-stack / AI) → run sections (secrets+supply-chain, DB, auth, infra+headers, legal, LLM/injection) orchestrating deterministic tools + manual checks → GO/NO-GO report. Adapted from Prajwal Tomar's playbook, extended with prompt-injection / supply-chain / secret-history / dependency-CVE layers. NOT the same as pre-push (that = clean push; this = is the product itself safe to launch). Triggers — "security checklist for the site", "audit before launch", "is the site safe", "check before handing to client".

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

Reports how local Git branches are progressing toward canonical upstream inclusion as a compact terminal table plus a browser-rendered HTML report, with branch purpose, stack dependencies, Git Machete topology, ahead/behind counts, change-request status, and next action. Use when asked for upstreaming status, local branch submission progress, which branches have change requests, or what remains before they can land.

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

Structures git branches and worktrees: keeps unrelated changes on separate branches, isolates each in its own worktree created so the repository's setup runs, records dependencies with git-machete, and recombines them into a temporary mixdown branch for local testing. Use before creating any branch or worktree in a codebase that works on more than one branch, including branching off the default branch to start a change; when starting work in a fork, clone, or third-party checkout; when choosing what a new branch should be based on; when a branch is growing a second unrelated concern; when deciding whether to stack branches or keep them independent; when preparing a change for a pull request or patch submission; when handed an existing worktree or branch to implement and commit in a fork; or when a local build needs several in-progress branches combined. Not needed where the repository clearly commits everything to the trunk, or holds notes or personal data rather than code.

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

Rebases every local branch of a fork onto a moved upstream, flags the ones upstream has superseded, and rebuilds the mixdown branch that combines them. Use after fetching a fork's upstream and finding it has advanced far, been force-pushed, or rewritten its history; when several stacked or sibling branches all need bringing forward at once; when a branch was cut from a mixdown and now carries merge commits it should not have; or when asked to rebase all branches, re-mix, or bring a whole worktree set up to date.

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