「concrete」の検索結果

Audit UIKit-based screens for accessibility issues with concrete VoiceOver and Dynamic Type fixes

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

Swift Concurrency review and remediation for Swift 6.2+. Use when asked to review Swift Concurrency usage, improve concurrency compliance, or fix Swift concurrency compiler errors in a feature or file. Concrete actions include adding Sendable conformance, applying @MainActor annotations, resolving actor isolation warnings, fixing data race diagnostics, and migrating completion handlers to async/await.

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

A hard-edged writing style contract for timeless, forceful English prose without modern AI tics. Use when users ask for prose or rewrites that must be clean, exact, concrete, and free of AI cadence, filler, or therapeutic tone.

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

Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.

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

GitHub Actions security review for workflow exploitation vulnerabilities. Use when asked to "review GitHub Actions", "audit workflows", "check CI security", "GHA security", "workflow security review", or review .github/workflows/ for pwn requests, expression injection, credential theft, and supply chain attacks. Exploitation-focused with concrete PoC scenarios.

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

Diagnose why a PostHog endpoint is slow or expensive and propose a concrete fix — bump the cache TTL, enable materialisation, restructure variables, or rewrite the query. Use when the user says "this endpoint is slow", "my endpoint times out", "we're hitting the cost cap on this one", or asks "should I materialise this?". Focuses on a single named endpoint, not a project-wide audit.

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

Assesses what a page's heatmap is telling you and recommends concrete changes. Pulls click / rageclick / scroll-depth data for a URL, names the hot elements by cross-referencing autocapture events on the same page, and can create a saved heatmap the user opens in PostHog, then summarizes the behavior and proposes improvements. TRIGGER when: user asks what a heatmap shows, why people aren't clicking something, where users rage-click, how far they scroll, what to change on a page based on heatmap/click data, or to 'analyze/assess/review the heatmap' for a URL. DO NOT TRIGGER when: the user only wants to create a saved heatmap screenshot with no analysis (use heatmaps-saved-create directly), or is asking about session replay in general (use investigating-replay).

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

Investigate errors, incidents, or product ideas using both internet research and repo-wide codebase research, then propose a concrete changeset plan with clarifying questions before any implementation. Use when a user asks to investigate, root-cause, or plan changes, or when an Issue or PR is referenced and needs a plan.

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

Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification in smart contracts via BLS12-381 host functions (CAP-0059, available), the BN254 + Poseidon proposals (CAP-0074/0075, status-sensitive), and concrete toolchain walkthroughs for Circom (on-chain verifiable today), Noir, and RISC Zero (attestation pattern until BN254 lands). Use when building privacy-preserving applications, ZK-verifier contracts, or wiring a proving toolchain to Stellar.

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

Queries the live CARLA world and resolves an entity description into a concrete actor id — find actors by type, role, or colour, or the single one nearest a point/actor; read the world snapshot; get static level bounding boxes by label; cast rays for semantic points; project a point to the ground; or (ros-topics) list the native ROS 2 topics each actor should be publishing and why any is silent. Identifies by stable attributes, not by any rank/order. Use when the user asks "what actors are here", "find the red prius", "the vehicle nearest the ego", "list the pedestrians", or needs a specific actor id for another skill.

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

Use when arranging the project quality-check or investigating a concrete unresolved code concern

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

Review and revise Japanese job-application documents (entry sheets, rirekisho, shokumu-keirekisho) by checking each answer against the question asked, the stated character limit, and the evidence the applicant can actually support, then propose concrete rewrites the applicant decides on. Use when a user wants an ES or resume answer critiqued, tightened, or drafted from their own experience; to assemble a whole shokumu-keirekisho from an experience inventory, use resume-draft instead; do not use to invent experience, to judge pass or fail probability, or to submit an application.

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

Detect articulation gaps in documents using 5W analysis and provide concrete improvement suggestions. Identifies what's missing in explanation, not what's wrong. Default runs detection + improvement; use --check-only for detection only. 旧名 check-articulation。

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

Ensure design/ADR changes include a concrete migration plan, rollout strategy, rollback conditions, and compatibility considerations.

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

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.

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

Design, implement, review, and audit Android Jetpack Compose UI/UX for phone interfaces. Use when a request concerns concrete Compose layout, components, interaction, accessibility, or visual behavior. Do not activate for framework or dependency presence alone; non-UI Android work is excluded.

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

A hard-edged writing style contract for timeless, forceful English prose without modern AI tics. Use when users ask for prose or rewrites that must be clean, exact, concrete, and free of AI cadence, filler, or therapeutic tone.

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

Raw, anti-design aesthetic inspired by concrete architecture with unadorned elements, jarring layouts, and functional minimalism.

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

Create a detailed, step-by-step implementation plan for a feature or project. Load when the user asks to plan a feature, create a technical roadmap, break down a PRD into tasks, design an implementation strategy, or sequence engineering work. Also triggers on "how should we build this", "implementation plan for", "technical breakdown", "task list for", or any request to turn a high-level requirement into a concrete execution plan. Supports phased rollouts, architecture-first, and MVP-focused planning.

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

Pick the right business-model canvas (Lean Canvas, Business Model Canvas, or Value Proposition Canvas) for the stage and fill it with specifics — one segment, one primary canvas, top-3 assumptions, no fluff in the moat or channel boxes. Load when the user asks to fill a business model canvas, lean canvas, value proposition canvas, model this business, map the business model, says "fill the BMC", "make a Lean Canvas", "Value Proposition Canvas for this", "model this idea", "what's the business model", "design the business model". Sub-skill of `venture-exploration`. Hard-bans "everyone" segments, generic channels ("SEO/social/content/ads"), and "unfair advantage = AI/data/network effects" with no concrete asset. Does NOT score viability — for that use `idea-evaluation`.

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

A hard-edged writing style contract for timeless, forceful English prose without modern AI tics. Use when users ask for prose or rewrites that must be clean, exact, concrete, and free of AI cadence, filler, or therapeutic tone.

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

Use this skill when the user asks about cargo securement requirements under 49 CFR 393 Subpart I — Working Load Limit (WLL), tiedown counts, tiedown types, commodity-specific securement rules (lumber, metal coils, paper rolls, concrete pipe, intermodal containers, vehicles, large boulders, dressed lumber, building materials), CVSA out-of-service criteria, and how to calculate aggregate WLL. Cite 49 CFR 393.100-136.

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

Select and configure a Coval metric for a concrete product criterion, choosing transcript, audio, trace or deterministic evidence and testing the result. Use for metric creation or scoring design, not for final human calibration.

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

Generates Strategy pattern for PHP 8.5. Creates interchangeable algorithm families with context class, strategy interface, and concrete implementations. Includes unit tests.

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