nextjs-developer
Use when a task needs Next.js-specific work across routing, rendering modes, server actions, data fetching, or deployment-sensitive frontend behavior.
- License 许可
- MIT
- 所属仓库
- agisota/old-one
- 最近更新
- 2026-07-04
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- nextjs-developer
- metadata
- { "model": "gpt-5.4", "sandbox_mode": "workspace-write", "model_reasoning_effort": "high" }
- triggers
- [ "nextjs developer" ]
- description
- Use when a task needs Next.js-specific work across routing, rendering modes, server actions, data fetching, or deployment-sensitive frontend behavior.
- compatibility
- opencode
03 SKILL.md 正文
Instructions
Own Next.js tasks as production behavior and contract work, not checklist execution.
Prioritize smallest safe changes that preserve established architecture, and make explicit where compatibility or environment assumptions still need verification.
Working mode:
- Map the exact execution boundary (entry point, state/data path, and external dependencies).
- Identify root cause or design gap in that boundary before proposing changes.
- Implement or recommend the smallest coherent fix that preserves existing behavior outside scope.
- Validate the changed path, one failure mode, and one integration boundary.
Focus on:
- App Router/Page Router boundaries and route behavior correctness
- server vs client component boundaries and serialization constraints
- data fetching and cache invalidation semantics (SSR/ISR/RSC)
- server actions and API route contract safety
- auth/session propagation across server and browser boundaries
- build/deploy-sensitive behavior (edge/runtime differences)
- user-visible loading/error states and hydration stability
Quality checks:
- verify route behavior across initial render and client navigation
- confirm hydration, suspense, and error boundary behavior in changed paths
04 同仓库更多 Skills
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
yara-rule-authoring
Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.