「orm」の検索結果

Auto-activate for Dockerfile, compose, Railway, Cloud Run, GKE, systemd, Kubernetes, Terraform, deploy scripts, or granian/litestar run at runtime. Not for packaging artifacts.

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

方案闭环：当用户显式调用 `$solution-loop`，或明确要求进入“方案闭环”时使用。 面向已经存在候选方案、但需要反方挑战和定点修订的场景，在 brainstorming Maker 与 grill-me Critic 之间最多循环三轮，直到方案确认或进入 Human Gate；不用于从零脑暴方案。

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

Perform comprehensive technical reviews of Ruby on Rails applications. Runs automated analysis tools (RubyCritic, Brakeman, bundler-audit, Gitleaks, Debride, linters, SimpleCov, Rails stats, Rails ERD), analyzes code for architecture, security, authorization (Pundit/CanCanCan), dead code, and design issues, and produces a structured markdown report with prioritized findings and a 0-10 score. Use when the user requests a tech review, code audit, project assessment, or quality analysis of a Rails application.

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

Use when predicting Threads post performance, analyzing post history patterns, estimating engagement ceiling for a draft, or deciding what content type to write next. Works with or without personal data — uses darkseoking benchmark as fallback.

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

Write an analytical longform piece — a 4-phase pipeline from raw idea to finished text, with research-backed facts and a devil's-advocate pass before publishing. Invoke /longread <topic>. Triggers — "write a longread about X", "write an analytical breakdown of Y", "write an expert post", "turn this into an article".

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

OWASP ASVS v5.0 security verification skill with Drupal 11 mappings. Use when performing security code reviews, implementing security requirements, or verifying security compliance in Drupal projects.

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

Phased workflow for delivering a Drupal feature or non-trivial change: plan, implement, review, test, finalize. Use when building a new custom module, adding a route/form/plugin, changing entity structure or schema, or any task touching more than a couple of files. Do NOT use for typo fixes, CSS tweaks, or single-line changes — use the tiny-fix skill instead. Each phase has an exit condition; do not move to the next phase until it is met.

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

Research complex questions and synthesize relevant evidence into a clear, cited answer. Useful for competitive and market analysis, company research, prospect discovery, enrichment, historical comparisons, and evaluating conflicting claims. Adapt the depth and format to the question; use when a focused search or single-page read is insufficient.

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

How to fetch the latest github/gh-aw release binary — either as the gh CLI extension (gh aw ...) or as a raw platform binary downloaded from GitHub Releases — including how to resolve the latest tag, pick the right asset, and verify its checksum.

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

Python code quality review lens. SOLID principles, dead code, exception handling, resource leaks, thread safety, performance. Triggered by "quality" ("품질"), "SOLID", "dead code" ("데드코드"), "exception", "resource leak", "thread safety" keywords.

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

GEODE CHANGELOG.md management rules. Version releases, change logging, scope determination, format standards. Triggers on "changelog", "release", "version", "릴리스", "변경사항", "버전".

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

Trigger when: (1) the user mentions "manim", "scene", "video", "EN/KO render", "GEODE_HERO_LANG", "1080p60", or (2) editing files under `scripts/visualizations/` ending in `.py`, or (3) the user asks to render, re-render, or extend any of the four validated scenes (`geode_hero.py`, `autoresearch_filewalk.py`, `autoresearch_compare.py`, `critical_floor.py`). GEODE Manim Scene authoring standard. Locks the patterns the four validated scenes already share — Anthropic-style palette, Helvetica Neue + Pretendard font pairing with weight=NORMAL, EN/KO multilingual lang via `GEODE_HERO_LANG` env, `_dashed_arrow_with_head` stage-coupled tinting, `verify_hero_layout.py` ratchet — so the next scene does not re-discover the kerning / padding / transition regressions catalogued in [[viz-frame-audit]].

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

Technical blog post writing guide. rooftopsnow.tistory.com style — Korean formal technical prose, architecture diagrams, code blocks + design intent commentary, table comparisons, checklist wrap-up. Triggers on "blog", "포스팅", "블로그", "기술 글", "tech blog".

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

Research process for comparing frontier harnesses (Claude Code, Codex, OpenClaw, autoresearch, Prime Agent) with the original/upstream implementation and performing GAP analysis before feature implementation. Triggered by "research" ("리서치"), "gap", "frontier", "harness", "case study" ("사례 조사"), "pattern exploration" ("패턴 탐색"), "comparative analysis" ("비교 분석") keywords.

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

Apply GEODE's measured architecture, module and symbol naming, Python type/class, persisted schema, test, site, and versioning conventions. Use when adding or moving modules, choosing dataclass/Pydantic/Protocol/ABC forms, naming classes or files, designing stored data, reviewing convention compliance, or deciding compatibility and release version treatment.

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

Reference when designing autonomous agent systems or deciding agent freedom/safety/context management/collaboration infrastructure. 10 design principles distilled from Karpathy autoresearch (autonomous ML experiment loop) + AgentHub (agent-native Git DAG). Triggered by "autoresearch", "agenthub", "ratchet" ("래칫"), "context budget", "dumb platform", "program.md", "overnight", "autonomous experiment" ("자율 실험"), "branchless", "single-file constraint" ("단일 파일 제약"), "fixed time budget" ("고정 시간 예산") keywords.

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

Mandatory 3-phase explore-reason-act workflow before code modification. Enforces read-before-write, root cause hypothesis formulation, minimal change application. Triggered by "explore" ("탐색"), "reason" ("추론"), "read before write", "root cause" ("근본 원인") keywords.

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

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

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

Generates a minimal .editorconfig with sensible defaults for a repository. Use when starting work in a new repository, when a project has no .editorconfig, or when the user asks to add or standardise editor and formatting settings.

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

Fetch and extract readable text content from a URL, then summarise or present key information.

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

Used by the Reviewer agent during Phase 9 (DesignVerify) and Phase 11 (Quality) to evaluate frontend code. Assesses visual hierarchy, spacing consistency, accessibility, and detects formulaic 'AI slop' design patterns, providing actionable feedback to the Developer.

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

Route database tasks to the right library skill. Covers migrations, query optimization, ORM, transactions.

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

Deep knowledge about deploying applications to Google Cloud Platform (Cloud Run, App Engine, Compute Engine).

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

Route deployment tasks to the right library skill. Detects intent and returns specific platform skill file paths to load.

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