「que」の検索結果

Create or refresh screenshot-led product hero images, localized interface captures, and image-led README sections for GitHub repositories. Use whenever a user asks to make a GitHub README show a GUI product visually, add software screenshots, design a README hero image, reproduce a screenshot-collage reference, or prepare repository-bound visual documentation. For GUI applications, default to the deterministic product-proof split hero with real software screenshots unless the user explicitly requests another visual direction.

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

Systematically test authorized targets for SQL, XSS, SSTI, XXE, command, and request-smuggling injection classes.

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

Validate database schema, migrations, indexes, and query behavior with structured pass/fail reporting.

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

Review a GitHub pull request and provide structured feedback with severity ratings

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

Analyze, design, write, revise, translate, and review empirical or technical research papers through an evidence-bounded dialectical workflow. Use when Codex must develop a research question, integrate reference papers with a user's ideas, build phenomenon-mechanism-conditions reasoning, design methods or experiments, restructure or edit a manuscript, translate Chinese academic text into restrained English, answer reviewers, or run multi-round peer-review convergence without fabricating evidence.

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

Draft or refine IDD-ready GitHub issues, roadmap issues, and sub-issues before the normal IDD execution loop begins. Use when a request is too large or ambiguous for one reviewable change, when work needs decomposition or dependency encoding, or when the user asks for issue drafting, roadmap planning, or parallelizable task breakdown.

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

Semantic audit of the IDD instruction corpus for leaked session context, cross-file contradictions, fresh-memory completability gaps, automation blockers, and restatement-discipline drift. Use on request to audit .github/instructions, the issue-authoring skill bundle, and the installed agent entry files (CLAUDE.md, AGENTS.md, GEMINI.md, .github/copilot-instructions.md). Read-only — never edits files or mutates issues.

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

Use this skill when planning, redesigning, or reviewing Xiaohongshu carousel visuals, covers, 3:4 image posts, page-by-page visual direction, image-generation prompts, style selection, layout critique, or XHS captions. It acts as a senior visual director for 小红书图文, not a generic copywriting assistant.

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

GStack plan-tune method for calibrating how many questions to ask, autonomy level, stop conditions, and decision style for a workstream or user preference.

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

GStack CEO/founder-mode plan review for strategy, customer value, scope, sequencing, business risk, and whether the work should be done now.

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

Produces a deep, honest peer-review of how someone uses Claude Code by statistically analyzing their local session data (~/.claude/usage-data/ and ~/.claude/projects/). Trigger whenever the user asks to review, analyze, audit, or critique their own Claude Code usage, workflow, habits, or skill level — including phrases like "analyze my cc usage", "review my cc sessions", "peer review my cc workflow", "deeper than /insights", or any ask for an honest audit of their AI workflow. Also covers portfolio/hiring-manager framings (e.g. "portfolio for Anthropic/OpenAI/xAI"), but ALWAYS ask the user in Step 0 which version to build (self / hr / both) before running — never silently produce an HR report, because that version goes to outsiders and needs explicit privacy setup. The HTML report is laid out ledger-first for SELF (opening band, output/team/leak/trend ledgers, then peer review, 9-dim scoring, try-this-week, case study, claim-indexed evidence). The HR variant is a recruiter version v1: identity card, earned badges (threshold-based, earned-only), allowlist-filtered output ledger, one case study, and a methodology & scope disclosure — no scores, no peer-review memo, no charts.

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

Triages GitHub issues and PRs into maintainer-facing cards: what each is, why it matters, author trust, risk, test and CI state, blockers, and next action. Use when the user says triage inside a repository or needs to work through an issue or PR queue.

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

Builds a compact profile of a GitHub user or PR author — identity, activity, company, commit history, and trust signals. Use during pull request review or triage, especially for contributions from unfamiliar authors.

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

Answers GitHub read questions from a local cache first and spends live API calls only when freshness or writes matter, with freshness policies for issues, PRs, and repos. Use when agent workflows hit GitHub rate limits or repeat the same API reads.

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

All changes to code must follow the guidance documented in the repository. Before any issue is filed, branch is made, commits generated, or pull request (or PR) created, a search must be done to ensure the right steps are followed. Whenever asked to create an issue, commit messages, to push code, or create a PR, use this skill so everything is done correctly.

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

Comprehensive guide for configuring and managing GitHub Dependabot. Use this skill when users ask about creating or optimizing dependabot.yml files, managing Dependabot pull requests, configuring dependency update strategies, setting up grouped updates, monorepo patterns, multi-ecosystem groups, security update configuration, auto-triage rules, or any GitHub Advanced Security (GHAS) supply chain security topic related to Dependabot. For pre-commit dependency vulnerability scanning in AI coding agents via the GitHub MCP Server, this skill references the Advanced Security plugin (`advanced-security@copilot-plugins`). Use this skill when an agent needs to scan dependencies for known vulnerabilities before committing.

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

Massimo Vignelli's complete design discipline — distilled from The Vignelli Canon. Encodes the Intangibles (semantics, discipline, appropriateness, timelessness, equity) and the Tangibles (the grid, the six basic typefaces, two-size type scale, rulers, primary-color-as-identifier, white space) into an applyable methodology. Use to design or critique identity systems, editorial layouts, wayfinding/transit signage, posters, and web pages in rigorous, timeless, Swiss-modernist Vignelli discipline. Triggers: "Vignelli style", "timeless design", "Swiss modernist", "design system", "transit signage".

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

Identifies Oracle-to-PostgreSQL migration risks by cross-referencing code against known behavioral differences (empty strings, refcursors, type coercion, sorting, timestamps, concurrent transactions, etc.). Use when planning migration of a procedure, trigger, query, or refcursor client, and again to validate the finished port.

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

PostgreSQL-specific development assistant focusing on unique PostgreSQL features, advanced data types, and PostgreSQL-exclusive capabilities. Covers JSONB operations, array types, custom types, range/geometric types, full-text search, window functions, and PostgreSQL extensions ecosystem. Use when writing or tuning PostgreSQL-specific SQL or choosing PostgreSQL features for a design.

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

Build hyper-personalized, narrative-driven, single-file portfolio/pitch websites in the style of anass.pro. Use when the user asks for a "site like anass.pro", a one-recipient candidacy/pitch site, a behavioral-engineering landing page, a single-file storytelling portfolio with a pixel-art game hero, custom cursor, typewriter text, procedural Web Audio SFX, scroll-revealed scenes, or a dark purple narrative interface that addresses one named reader. Trigger on phrases like "personal pitch site", "one-page candidacy", "narrative portfolio", "scrollytelling pitch", "pixel-art hero", "interactive landing for X", or any request to recreate / clone / adapt anass.pro.

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

Designs, critiques, audits, and polishes frontend interfaces — websites, landing pages, dashboards, components, onboarding, and empty states — after loading the project's PRODUCT.md and DESIGN.md context. Use when the user wants to design, redesign, review, or improve a UI.

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

This skill enables visual inspection of websites running locally or remotely to identify and fix design issues. Triggers on requests like "review website design", "check the UI", "fix the layout", "find design problems". Detects issues with responsive design, accessibility, visual consistency, and layout breakage, then performs fixes at the source code level.

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

Build editorial/magazine/report webpages on a GENUINE Müller-Brockmann modular grid (International Typographic Style). Encodes the discipline (columns + modules + baseline, grotesque type, flush-left, restrained black/white/red palette) AND the front-end engineering to make the grid real, visible, and verified: one CSS-variable source of truth, an interactive grid-toggle overlay, subgrid bands, 8px baseline lock, and runtime optical alignment. Triggers: "magazine spread", "grid system", "Swiss design", "editorial layout", "show the grid", "align everything to the grid".

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

Use when working with Entity Framework Core — modeling entities and relationships, migrations, LINQ query performance, change tracking, N+1 problems, and connection and transaction handling.

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