Open source · First-party agent guidance

Give capable agents better judgment.

Install focused workflows and optional standing conventions for the parts models tend to gloss over: missing evidence, specialist tradeoffs, authority boundaries, and the checks that make a result ready for review.

effective disciplines
6
focused references
336
optional instruction packs
2
Start with Your task not our taxonomy
Each discipline is useful on its own. Add another only when the work crosses a real boundary.
Try one discipline npx skills add sebastian-software/skills.sebastian-software.com --skill effective-web
Install one discipline Ask in normal language Load only relevant guidance Inspect every workflow Verify before done

Choose by need

What do you need your agent to do?

Bring the brief, repository, interface, or rough idea you already have. The right discipline gives the agent a professional route through the work without pretending missing evidence or authority does not matter.

Pick the outcome

Job to be done Start with · Research, notes, or a brief

Turn uncertainty into a product decision.

Make the agent separate facts from assumptions, connect customer evidence to strategy, and define the smallest responsible next move.

The agent learns to Decide from evidence

Unknowns remain visible instead of being polished into false certainty.

Relevant disciplines
  • StartEffective Product
  • RouteDiscovery · Strategy · Scope
  • RecordDecision Records route
You get

A recommendation with explicit evidence, tradeoffs, scope, and learning conditions.

  1. 01Relevant context

    The agent inspects the evidence and local rules before proposing answers.

  2. 02Narrow guidance

    Only the routes and references needed for the current task are loaded.

  3. 03Clear boundaries

    Unknowns, missing authority, and specialist handoffs stay explicit.

  4. 04Finish criteria

    The skill defines what must be checked before the work is called complete.

A useful first discipline

Give your agent a real web task and the repository it belongs to.

Explore Effective Web
npx skills add sebastian-software/skills.sebastian-software.com --skill effective-web

From one discipline to a workflow

Use one discipline. Add another when the work truly crosses a boundary.

Each discipline is portable and independently useful. They also share one naming grammar and one evidence-led quality bar, so handoffs stay explicit when a task moves from product direction through design, delivery, and communication.

  1. 01

    Decide

    Make the right product call.

    Gather the evidence, then turn it into direction, scope, priorities, pricing, names, and durable decisions.

  2. 02

    Create

    Build it as one system.

    Connect the browser experience with the architecture, data, and code underneath it.

  3. 03

    Improve & deliver

    Move repositories forward with evidence.

    Coordinate, audit, modernize, document, port, update dependencies, review, and deliver without losing correctness or context.

  4. 04

    Reach

    Explain the value like a human.

    Turn expertise into positioning, credible content, useful conversations, and clear team communication.

The broadest discipline

Frontend work rarely stays in one discipline.

Effective Web routes broad frontend work through the smallest relevant guidance set, then checks the result across design, implementation, accessibility, performance, and verification boundaries.

28intent routes
132focused references
1coherent quality bar
Explore Effective Web
Design planning & review Accessibility React architecture Forms UX Performance CSS architecture Typography Frontend SEO & AI search Motion SVG Data tables Testing Auth UX Internationalization & RTL Web-to-print

Six effective disciplines

Install the judgment your agent is missing.

Every discipline has a human-facing overview, an explicit trigger, a routing table, clear boundaries, and its own selective install path.

Product01

Effective Product

Decide what to build and how it should work: research, discovery, strategy, scope, design modeling, pricing, naming, and decision records.

  • 10 intent routes
  • Evidence before answers
Explore skill
Web02

Effective Web

Design, build, review, and improve production web experiences as one connected system, from reference capture to compliance.

  • 28 routed workflows
  • Design to verification
Explore skill
Engineering03

Effective Engineering

Design and write the software itself: architecture, data models, TypeScript and Rust depth, focused tests, and benchmark methodology.

  • 9 intent routes
  • Contracts, not conventions
Explore skill
Delivery04

Effective Delivery

Move an existing repository and the team around it forward: audits, ports, PR review, delegated issue queues, dependencies, checks, docs, and leadership.

  • 10 intent routes
  • Authority stays explicit
Explore skill
Writing05

Effective Writing

Prose people trust and act on: structure and revision, AI-pattern audits, natural US team English, and locale typography.

  • 7 intent routes
  • Never invents facts
Explore skill
Marketing06

Effective Marketing

Take verified value to market: positioning, messaging, launch, copy, conversion, social strategy and content, LinkedIn, and profile positioning.

  • 12 intent routes
  • Claims trace to proof
Explore skill

Why these skills exist

More instructions are not the point.

The value is better judgment at the moments generic guidance usually leaves implicit.

  1. 01

    Practice-built

    Distilled from engineering, design review, product work, consulting, and repeated agent sessions.

  2. 02

    Evidence-led

    Repository state, user data, research, and observed behavior outrank confident assumptions.

  3. 03

    Outcome-oriented

    Discovery, implementation, review, verification, and delivery stay connected.

  4. 04

    Progressively disclosed

    Agents load the smallest useful route and references, not the whole library every time.

  5. 05

    Explicit about boundaries

    Every skill states what it must not invent and when a specialist workflow is needed.

Two portable asset types

Guidance here. Activation stays explicit.

Skills provide task-triggered professional depth. Optional instruction packs provide standing cross-task conventions such as request authority, completion, and documentation truth. Every skill still works alone; DALO or a downstream agent stack decides which packs become active, where they are projected, and how they coexist with external catalogs and project instructions.

Read the collection boundary

Start with one. Grow deliberately.

Add one useful workflow in a minute.

Both the skills CLI and DALO support selective installation. You do not need to adopt the full collection to use one skill.

01

Quick install

skills CLI

Try one skill immediately with any compatible agent environment.

npx skills add sebastian-software/skills.sebastian-software.com --skill effective-web

Replace effective-web with any skill name, or pass --all.

02

Managed setup

DALO

Install DALO, initialize its configuration, link an agent target, and pin the reviewed selection.

curl -fsSL https://dalo.sh/install.sh | sh dalo init dalo target link codex dalo source add-catalog sebastian https://github.com/sebastian-software/skills.sebastian-software.com.git dalo source select sebastian effective-web dalo approve skill sebastian:effective-web dalo sync dalo instructions enable sebastian:request-and-completion --target codex dalo instructions enable sebastian:documentation-truth --target codex

Skills and instruction packs activate separately. The final commands require a DALO release with source-backed packs.

Built in the open

Professional practice, made portable.

Sebastian Software builds and supports open-source software and helps teams design, modernize, and ship ambitious software products. This collection turns that practical experience into inspectable, reusable agent workflows.