Apply these opinionated Next.js conventions whenever writing or reviewing App Router code (14+): Server Components by default, where the 'use client' boundary belongs, the caching defaults that changed in Next 15, tag-based revalidation, treating Server Actions as public endpoints, the Metadata API, and next/image and next/font.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
House conventions for Next.js App Router (14+). Apply them to code you are writing or changing — don't migrate untouched routes unless asked.
pages/. If a project still has one, new work goes in app/ and the two coexist until someone schedules the migration.'use client' marks a leaf that needs interactivity, not a page. Everything above that marker ships to the browser too, so the boundary belongs as deep in the tree as it will go.fetch was cached by default and you opted out; from Next 15, fetch, Route Handlers, and client navigation are uncached by default and you opt in. Assuming the wrong default gives you either stale pages or an origin taking every request. Check package.json, then set the intent explicitly (cache, next.revalidate, or route segment config) rather than relying on whatever the default happens to be.params and searchParams are Promises from Next 15 on — const { slug } = await params. Code written against 14 destructures them synchronously and breaks on upgrade, so check the installed major before copying either form.layout.tsx auth check is not a security boundary. Layouts don't re-render on every navigation between their child routes, so the check can be skipped on client-side transitions. Enforce access in middleware and again where the data is read; the layout check is UX, not enforcement.next: { tags: ['user'] } plus revalidateTag('user') after a mutation invalidates exactly the affected data. Time-based revalidation is a guess about staleness; tags are a fact about it.export const metadata or generateMetadata. Hand-written <head> tags in a component don't merge across nested layouts and silently lose out to the framework's.next/image and next/font always. They exist for the two largest Core Web Vitals costs: unsized images causing layout shift, and font loading blocking first paint. A raw <img> gives up both.loading.tsx and error.tsx per meaningful route segment. The route boundary is where a failure should be contained; without error.tsx, one segment's error takes down the layout around it.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Apply these opinionated C# conventions whenever writing or reviewing C# 12 / .NET 8+ code: nullable enabled with warnings as errors, records and primary constructors, pattern matching over cast chains, the Result pattern for expected failures, async all the way with CancellationToken, IOptions config, IHttpClientFactory, and never returning EF entities from an API.
日本語の概要は準備中です。原文の説明を表示しています。
ALWAYS invoke for any task involving docstrings, JSDoc/TSDoc, or REST API documentation — even when the request seems handleable without it. Enforces Microsoft contract-first conventions and a bare-minimum rule that Claude won't apply by default: never restate the signature, drop @param/@returns that only echo names and types, always document @throws, and document data shapes as WHAT not WHY. Covers Python docstring styles (Google/NumPy/Sphinx), TSDoc tags and @inheritDoc, and API doc patterns for NestJS/Express/FastAPI/Django. Trigger on: adding or auditing docstrings, redundant or missing tags, deleting comment rot, or producing a documentation-health report. Do not skip for documentation tasks — consistent conventions are the whole point.
日本語の概要は準備中です。原文の説明を表示しています。
Apply these opinionated .NET 8 architecture conventions whenever structuring or reviewing a backend service: clean architecture layering and which direction dependencies point, when CQRS with MediatR is worth it, cross-cutting concerns as pipeline behaviours, minimal APIs grouped by feature, keeping DbContext in Infrastructure, health checks and structured logging, WebApplicationFactory integration tests, and when AOT pays off.
日本語の概要は準備中です。原文の説明を表示しています。
Remove signs of AI-generated writing from text. Use after drafting to make copy sound more natural and human-written. Based on Wikipedia's "Signs of AI writing" guide.
日本語の概要は準備中です。原文の説明を表示しています。
Apply these opinionated JavaScript conventions whenever writing or reviewing JS or Node: ESM-first packaging, choosing between Promise combinators, error handling that doesn't swallow failures, AbortController for cancellation, keeping the event loop unblocked, and reaching for platform APIs before dependencies.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the git commits for a Jira ticket into a short, business-friendly implementation report and save it as local markdown. Use when the user wants to report finished work on a Jira ticket: a Jira report, update, or comment, a summary of their commits or changes for the ticket, or a note telling PM/QA what shipped.
日本語の概要は準備中です。原文の説明を表示しています。