choose-dev-entrypoints

Name: choose-dev-entrypoints
Availability: InStock
Author: darkmatter

Choose dev entrypoints and responsibility boundaries across Nix, Just, and scripts.

1|Updated Apr 27, 2026

Search Tags:#nix #bun #scripts #turbo #just #dev-workflow #shellhook

Ready to run

npx skills add https://github.com/darkmatter/skills --skill choose-dev-entrypoints

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: choose-dev-entrypoints
Source: https://github.com/darkmatter/skills/tree/main/skills/choose-dev-entrypoints
Command: npx skills add https://github.com/darkmatter/skills --skill choose-dev-entrypoints

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you decide which layer should own each development workflow so your repo stays fast to enter, easy to understand, and simple to maintain.

Core Features & Use Cases

Responsibility Mapping: Separates what belongs in Nix, shell hooks, package scripts, task runners, Just, and imperative scripts.
Workflow Design: Guides decisions for dev, build, test, install, code generation, and local service startup entrypoints.
Repository Ergonomics: Helps keep environment setup cheap, cacheable, and delegated to the lowest layer that truly needs the work.

Quick Start

Help me choose the right dev entrypoint for this repository by comparing nix develop, shellHook, just, package scripts, turbo, and ./scripts, then recommend the cleanest responsibility split.

Frequently Asked Questions about choose-dev-entrypoints

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I choose the right dev entrypoint for my repository?▼

Choosing the right dev entrypoint requires a layered delegation model that assigns ownership to the lowest capable layer, keeping shell entry cheap and workflows cacheable across Nix, Just, Bun scripts, and Turbo tasks.

What is the best way to split responsibilities between Nix shellHook and Just scripts?▼

Split responsibilities by keeping environment setup in Nix shellHook and delegating imperative task running to Just scripts, ensuring the shell entry remains fast while preserving understandable and cacheable workflows.

When should I use Turbo tasks instead of package scripts for build and test workflows?▼

Use Turbo tasks for build and test workflows when you need cacheable, delegated task execution across a monorepo, whereas package scripts are better suited for simpler, localized command execution within a single package.

Does Nix develop work well with Bun scripts and Turbo for local service startup?▼

Nix develop works well with Bun scripts and Turbo by providing the isolated environment, while Bun and Turbo handle service startup and task delegation, maintaining a clean separation between environment setup and command execution.

Why does my dev workflow slow down when putting code generation in shellHook?▼

Dev workflows slow down because shellHook executes on every shell entry, so placing heavy operations like code generation there violates the cheap shell entry principle and increases startup latency.

Do I need a ./scripts directory if I already use Just for dev, build, and install commands?▼

You might still need a ./scripts directory for imperative, one-off commands that do not fit Just's declarative task model, keeping Just focused on repeatable, cacheable dev, build, and install workflows.