「strict」の検索結果

Audit essays, reports, literature reviews, dissertations, proposals, and source-backed assignments for high-score academic quality. Use when the user asks whether a paper can get a high grade, wants teacher/rubric feedback addressed, needs a pre-submission review, or needs checks for strict rubric compliance, academic standards, prompt/rubric alignment, argument quality, comparative analysis, evidence hierarchy, table/figure integration, citation specificity, conclusion strength, academic language, source-claim integrity, or evidence boundaries.

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

Revise an already accepted article, essay, paper, statement, or manuscript under strict minimal-change constraints while still satisfying reviewer comments, supervisor feedback, or requested edits. Use when the user asks for minimal edits, smallest necessary changes, preserve the current voice, keep the existing style, avoid broad rewriting, or implement requested revisions without unnecessary polishing.

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

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

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

Strict test-driven development for behavior changes. Requires verified RED before production code, minimal GREEN, and refactor only after passing tests.

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

用于创建、配置、审查或调试前端应用、库、SDK、CLI、monorepo 包中的 TypeScript 项目规范，包括 tsconfig、strictness、module/moduleResolution、路径别名、project references、声明文件、package exports、公共 API 类型、DTO、高级泛型、判别联合、类型守卫、类型收窄或类型级回归。React/Vue/Next/Nuxt 组件架构优先使用框架项目 skill；中文触发词包括 TypeScript 项目规范、TS 项目规范、TypeScript 类型安全、类型建模、泛型、判别联合、类型收窄、tsconfig、声明文件。

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

Use when creating, configuring, reviewing, or debugging TypeScript project standards across frontend apps, libraries, SDKs, CLIs, monorepo packages, tsconfig, strictness, module/moduleResolution, path aliases, project references, declaration files, package exports, public API types, DTOs, advanced generics, discriminated unions, type guards, type narrowing, or type-level regressions. Prefer framework project skills for React/Vue/Next/Nuxt component architecture; Chinese triggers include TypeScript project specification, TS project specification, TypeScript type safety, type modeling, generics, discriminative unions, type narrowing, tsconfig, declaration files.

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

Use when a task needs the judgment of an EMT (Basic Life Support tier) — deciding whether a chest-pain patient gets aspirin under protocol, dosing an epinephrine auto-injector for anaphylaxis and knowing when to repeat it, applying spinal-motion-restriction criteria instead of routine backboarding, recognizing the moment a call exceeds BLS scope and requesting ALS intercept, or working a patient refusal (AMA) to a legally defensible conclusion.

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

Use when a task needs the judgment of a correctional services manager (warden/facility administrator) — deciding how to respond to a staffing cut against safety risk, reviewing an inmate classification or housing decision, evaluating a use-of-force incident, deciding whether restrictive housing placement is justified and time-limited, or weighing security spending against programming budget under fiscal pressure.

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

Use when a task needs the judgment of a Brownfield Redevelopment Specialist and Site Manager — confirming landowner liability protections (BFPP/AAI) before a contaminated-site acquisition closes, matching a cleanup standard to the actual reuse plan instead of defaulting to the most conservative one, sequencing a brownfield funding stack (EPA grants, state VCP, tax credits) by eligibility dependency, or deciding whether an institutional control/deed restriction needs disclosure to a lender or buyer.

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

Use when a task needs the judgment of a Bridge and Lock Tender — deciding whether to open a movable span for a vessel signal during a restricted-hours window, sequencing a lock chamber's fill/empty and valve staging, verifying an interlock/gate cycle before commanding span movement, resolving a marine-traffic-vs-vehicle-traffic conflict, or coordinating a vessel passage over VHF.

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

Use when a task needs the judgment of an archivist — appraising whether a donated or transferred collection has enduring value, deciding a processing level for a backlog, writing a finding aid, triaging preservation under budget constraints, or resolving a records-restriction question.

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

Use when a task needs the judgment of an Adapted Physical Education Specialist — writing a legally-defensible PE present level and annual goal from motor/fitness assessment data, choosing the right test battery and alternate items for a student's mobility profile, recommending a placement step on the PE least-restrictive-environment continuum, or distinguishing a motor/balance deficit from a behavioral avoidance pattern.

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

Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER models/agents to execute. Strictly read-only on source code — never implements, fixes, or refactors anything itself. Use when asked to audit a codebase, find improvement opportunities (bugs, security, performance, test coverage, tech debt, migrations, DX), suggest features or where to take the project next (roadmap, product direction), or generate handoff plans for another agent to implement.

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

FrontendHire's job-search operating system (fh) — a strict pipeline tracker, deterministic weekly metrics, and a review ritual. Runs the search as a measured system where the philosophy is law. Use for logging applications/leads/referral asks, the weekly review, status/metrics, and the onboarding interview.

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

Use when building Python 3.11+ applications requiring type safety, async programming, or robust error handling. Generates type-annotated Python code, configures mypy in strict mode, writes pytest test suites with fixtures and mocking, and validates code with black and ruff. Invoke for type hints, async/await patterns, dataclasses, dependency injection, logging configuration, and structured error handling.

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

Review Circuit Weaver's exhaustive placement proposal and apply approved SVG coordinates to a real electrically annotated KiCad PCB. Use after schematic generation for placement optimization, official-reference review, interactive SVG editing, strict reference reconciliation, and PCB placement handoff. Do not treat review artifacts as fabrication data.

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

Create, write, or manage Meta ads and assets: ad copy, campaigns, spend, reports, audiences, catalogs, product feeds, feed refresh schedules, experiments, and policy. Always load for any request to create or write an ad, or to advertise a product or service, even when no platform is named; this includes sensitive or restricted categories. Always load for any question asking what a Meta, Facebook, or Instagram advertising policy means, allows, prohibits, or requires, including a standalone policy-definition question with no account context. Those questions must use ads_policy_tool, never browser search or memory. Load for a specifically named catalog or feed with an upload or refresh-schedule request; use Ads reads to resolve ownership before writing. Generic unnamed feeds need context. Whether an image, claim or piece of copy may be used in an ad is ALWAYS a Meta Ads task — 'can I use this in an ad', 'is it allowed', 'is this against policy', and any rights, likeness, celebrity, logo or trademark question about advertising with an image, including a follow-up about one just generated. Those are ads-policy questions, not general legal ones. An ad request uses the campaign workflow unless explicitly only an image or organic post.

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

Deep codebase cleanup — kills dead code, fixes all lint/format warnings, removes orphaned files, cleans stale TODOs, strips security hazards, tightens TypeScript strict mode, and organizes imports. Triggers: clean up, dead code, unused imports, lint, technical debt cleanup.

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

**WORKFLOW SKILL** — Create custom VS Code Copilot agents (.agent.md). USE FOR: new agents, tool restrictions, handoffs, orchestration patterns, discipline constraints. DO NOT USE FOR: general coding, VS Code extension development.

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

Edit academic prose in LaTeX manuscripts or supplied text at light, moderate, or strict intensity. Improve grammar and clarity while preserving scientific claims, uncertainty, numbers, citations, and LaTeX structure.

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

Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an explicit stop condition matter.

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

Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (`audit_cluster.sh`), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (`gVisor`), enforcing Pod Security Standards (`restricted` labeling), and mounting Secret Manager secrets via CSI (`SecretProviderClass`). Use when auditing cluster security posture, isolating namespaces, applying pod security standards, setting up Workload Identity, or configuring network policies and secret volume mounts. Don't use for cluster-wide control plane security, RBAC hardening, Binary Authorization, Shielded Nodes, or enabling platform-level GKE add-ons (use gke-platform-security instead).

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

Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto Provisioning configuration or general GKE cluster creation.

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

Configure single-project Google Cloud Logging: regional log buckets, log sinks, log views, restricting or hiding sensitive logs in the default view (_Default) filter, IAM permissions for views (Logs View Accessor, IAM conditions), logs-based metrics, log exclusions, and sampling. Don't use for cross-project logging or multi-project setups.

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