4d V21

Data-Oriented-Design-for-Games/data-oriented-design

Language-agnostic architecture guide for building games and performance-sensitive apps with Data-Oriented Design (DOD) — adapted from *High Performance Unity Game Development (Using data-oriented design)* by Nitzan Wilnai, generalized to any language and with a first-class HTML5/JavaScript/Canvas track. Use this skill whenever building or reviewing a game (or real-time/simulation code) in DOD style outside Unity — especially HTML/JS/Canvas, but also C, C++, Rust, Go, Zig, or plain C#. Trigger when the user asks to: scaffold a game or feature in DOD style, generate DOD-compliant code, review co

SeanCole02/cl1-base

Build or adapt baseline CL1 human-neuron models, stimulation loops, and evaluation workflows. Use when Codex needs to design or modify CL1 training code, UDP stimulation and spike protocols, safe stimulation ranges, Same Frame Encoding (SFE), ablations, feedback-channel logic, or hardware-aware data and training loops for CL1 systems.

basejb/isms-p-audit-skill

ISMS-P 인증 사전 점검을 위한 코드/IaC 정적 분석 스킬. 사용자가 "ISMS 점검", "ISMS-P 준비", "보안 감사", "통제항목 점검", "개인정보보호 감사", "정보보호 인증 준비"를 언급하거나, NestJS/ Spring/Django/Rails 같은 백엔드 프로젝트에서 IAM·로깅·암호화·접근통제 미흡 사항을 식별해 달라고 요청할 때 호출한다. Glob/Grep/Read로 코드와 Terraform/CloudFormation/Kubernetes 매니페스트를 스캔해 ISMS-P 통제항목과 매핑된 리스크 보고서를 생성한다. EN: Static analysis skill for ISMS-P (Korean Personal Information & Information Security Management System) pre-audit. Triggers on phrases like "ISMS audit", "ISMS-P readiness", "security compliance check", "Korean privacy audit". Scans source code and IaC to map findings to ISMS-P controls and

felipereisdev/user-stories-skill

Analyzes a codebase and breaks down a goal into implementable user stories with clear acceptance criteria. Use when planning a new feature, estimating work, or creating a development roadmap. Explores the code before asking anything; when the goal is ambiguous, asks at most 5 blocking multiple-choice questions with a recommended answer, and records assumptions and open questions in the plan. Outputs execution-ready stories (schema v2: type, status, a verify check per criterion, dependencies with reasons, interfaces, files to reuse, file conflicts for parallel work) to .context/[goal-slug]-plan

fourierwang66666/product-requirements-review

Conducts structured product requirements review from idea to design doc. As PM asks clarifying questions; analyzes essence (problem, audience, real demand, business logic); researches competitors and data; as CTO assesses technical feasibility and Vibecode cost/time; then proposes creative, shortest-path solutions (smart, non-generic, with unique value or cold-start); makes go/no-go; if go, produces concept, name, architecture, user flows, system design (Vibecode-oriented), design references, and full design document. Principles: no process for its own sake, challenge ideas directly, common se

omarkilani/perf-hints

Improve C++ (C++11+) performance using Abseil “Performance Hints” (Jeff Dean & Sanjay Ghemawat): estimation + profiling, API/bulk design, algorithmic wins, cache-friendly memory layout, fewer allocations, fast paths, caching, and compiler-friendly hot loops. Use for performance code reviews, refactors, and profiling-driven optimizations. Keywords: performance, latency, throughput, cache, allocation, memory layout, InlinedVector, string_view, Span, flat_hash_map, pprof, perf.