Skip to main content
Jeden Skill in Manus ausführen
mit einem Klick
GitHub-Repository

whatisoffside

whatisoffside enthält 2 gesammelte Skills von frostney, mit Repository-Berufsabdeckung und Skill-Detailseiten auf SkillsMP.

gesammelte Skills
2
Stars
0
aktualisiert
2026-07-05
Forks
0
Berufsabdeckung
1 Berufskategorien · 100% klassifiziert
Repository-Explorer

Skills in diesem Repository

react-stack
Softwareentwickler

Defines the user's default React-based stack across two project profiles — web (Next.js App Router) and universal (Expo Router) — sharing a common core (Bun-only, TypeScript, Tailwind on web / React Native StyleSheet on native, co-located bun test, single aggregator check, Vercel AI Gateway, Clerk auth, Convex data, Plop scaffolding, Lefthook pre-commit, AGENTS.md hard constraints), carrying the React-specific project structure (src/app routing both profiles, Atomic Design component folders, one-export-per-file naming where the filename matches the export), and pointing to convex-conventions and project-structure for deeper specifics. Use when scaffolding a new React-based app, upgrading deps, choosing tooling for an MVP, or deciding which profile a project belongs to.

2026-07-05
software-engineering-excellence
Softwareentwickler

Ambient engineering-quality standard sitting above the execution/workflow skills that defines what good and excellent work means: grounding in reality, full-scope completeness, reuse over duplication, real validation, right-sized value, and maintainability as the governor. It is the default, not an add-on, and MUST be selected for planning, orchestrating, developing, debugging, reviewing, refactoring, changing architecture or test harnesses, or substantial technical investigation, even when no instruction asks for "quality". It stops the agent improvising its own definition of good, narrowing scope, shipping only the happy path, patching a symptom over a structural problem, duplicating code, treating docs or comments as proof instead of leads, swapping a decided approach, over-correcting after feedback, or claiming work is done without verifying it. Use when beginning, planning, or coordinating technical work, and especially after a correction or when scope, tooling, validation, or architecture might drift.

2026-07-05