2d-games
無料2D game development principles. Sprites, tilemaps, physics, camera.
日本語の概要は準備中です。原文の説明を表示しています。
4,258 件 ・ 関連度順
概要と使いどころ
2D game development principles. Sprites, tilemaps, physics, camera.
日本語の概要は準備中です。原文の説明を表示しています。
3D game development principles. Rendering, shaders, physics, cameras.
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing, reviewing, refactoring, or enforcing Angular application architecture with isolated lazy features, eager core/layout, reusable ui/pattern architecture building blocks, one-way dependency graphs, eslint-plugin-boundaries rules, or folder placement decisions. This skill takes precedence over angular-developer when architecture rules conflict with general Angular advice.
日本語の概要は準備中です。原文の説明を表示しています。
Use fresh agents for focused subtasks to avoid context pollution
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when asked to "create a plugin", "build a new plugin", "make a Claude Code plugin", "scaffold plugin", "plugin structure", "add commands/agents/skills/hooks to plugin", or when helping with plugin development.
日本語の概要は準備中です。原文の説明を表示しています。
Use when planning or upgrading an internal skill/workflow for business operations, especially when turning a messy idea into a structured skill plan, migration plan, acceptance checklist, or packaging decision. Particularly useful for Obsidian knowledge base consolidation, workspace migration, content library cleanup, and integrating multiple workbenches into one operating system.
日本語の概要は準備中です。原文の説明を表示しています。
Start the Wasp dev server and set up full debugging visibility. This includes running the server (with access to logs), and connecting browser console access so the agent can see client-side errors. Essential for any development or debugging work.
日本語の概要は準備中です。原文の説明を表示しています。
Guides Quarkus development across REST APIs, CDI dependency injection, Hibernate ORM, Panache, configuration, OpenAPI, templates, messaging, security, observability, packaging, and tooling. Use when building Quarkus applications, adding endpoints or clients, configuring datasources or OIDC, debugging build or runtime issues, or choosing extensions.
日本語の概要は準備中です。原文の説明を表示しています。
Resolve repository documentation authority, repair reading paths and explanations, or shape a bounded public projection. Maintain docs after a bounded change when indirect reader promises, generated or paired sources, version/evidence boundaries, or unclear authority need attention. Ordinary known updates stay in normal development; not for isolated prose polishing, code review, or broad runtime audits.
日本語の概要は準備中です。原文の説明を表示しています。
Report the current development environment: Node, Python, OS, git state. Use when debugging environment issues, onboarding, or checking system compatibility.
日本語の概要は準備中です。原文の説明を表示しています。
Help build and optimize 3D games and interactive experiences on Android, using engines and frameworks.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level medicinal chemistry knowledge. Use when working with drug design, structure-activity relationships, ADMET properties, pharmacophores, lead optimization, target identification, drug metabolism, or pharmaceutical development. Also use when the user mentions 'SAR', 'drug design', 'pharmacophore', 'ADMET', 'lead compound', 'hit to lead', 'drug metabolism', 'bioavailability', 'selectivity', 'binding affinity', 'scaffold hopping', or 'bioisostere'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing any feature or bugfix, before writing implementation code
日本語の概要は準備中です。原文の説明を表示しています。
Use when executing implementation plans with independent tasks in the current session
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
日本語の概要は準備中です。原文の説明を表示しています。
Elite full-stack developer for rapid spec and implementation. Use when the user asks to talk to Barry or requests the quick flow solo dev.
日本語の概要は準備中です。原文の説明を表示しています。
Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, valid manifest defaults, and personal-marketplace entries by default. Use when Codex needs to create a new personal plugin, add optional plugin structure, generate or update marketplace entries for plugin ordering and availability metadata, or update an existing local plugin during development with the CLI-driven cachebuster and reinstall flow.
日本語の概要は準備中です。原文の説明を表示しています。
Domain-Driven Design system for software development. Use when designing new systems with DDD principles, refactoring existing codebases toward DDD, generating code scaffolding (entities, aggregates, repositories, domain events), facilitating Event Storming sessions, creating bounded context maps, or performing code reviews with a DDD lens. Covers both strategic design (bounded contexts, subdomains, context maps, ubiquitous language) and tactical design (entities, value objects, aggregates, domain services, repositories). Supports all major architecture patterns (Hexagonal/Ports & Adapters, CQRS, Event Sourcing, Clean Architecture) with language-agnostic guidance and concrete examples in Python and TypeScript.
日本語の概要は準備中です。原文の説明を表示しています。
Creates LinkedIn posts, thought leadership content, and editorial calendars for SME marketing. Covers 7 post types (Awareness, Personal Story, Education, Conversion, How We Do It, Building In Public, Lead Magnet) with complete graphic prompts, first comments, and CTAs. Use when user asks to write social media posts, plan content calendars, create LinkedIn content, or develop thought leadership pieces.
日本語の概要は準備中です。原文の説明を表示しています。
Assess development requests, then execute and resume complete TaskBelay tasks in ZCode with Core-owned state.
日本語の概要は準備中です。原文の説明を表示しています。
Assess development requests, then execute and resume complete TaskBelay tasks in Claude Code with Core-owned state.
日本語の概要は準備中です。原文の説明を表示しています。
Assess bounded Codex software development requests before choosing direct work or TaskBelay, then prepare confirmed TaskBelay Tasks in new local branches by default, current branches, or dedicated Git worktrees. It may be selected implicitly or explicitly with $taskbelay-codex:taskbelay; the selector never skips assessment. Explicit Task resume and receipt-backed confirmed bootstrap bypass duplicate assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Check proposed stack, data flows, cloud choices, and delivery controls against declared enterprise policies, compliance frameworks, and security controls. Trigger at R2/R3 risk classification, before locking architecture decisions, or when the operating profile names a governance pointer.
日本語の概要は準備中です。原文の説明を表示しています。