• Our process

    Five steps from idea to a product that keeps improving.

  • Engagement models

    Spec & quote projects, an agile retainer or team augmentation.

  • Our tools

    The playbook, CMS and project tools we built and use every day.

  • Company

    A boutique digital agency in Cedar Grove, NJ, since 2001.

  • What We Believe

    What we believe and how it shapes the way we work.

  • Team

    Meet the designers, developers and strategists.

  • Testimonials

    What our clients say about working with us.

  • Insights

    Ideas on software, AI and agents from our team.

Design-Led, AI-First /// Est. 2001

Our playbook for Claude Code and Codex

The standards, guardrails and reviewer agents our engineers work inside every day. It makes AI-written code safe to ship, and we install it for your team too.

Let’s Talk
Pete Czech, CEO and founder of NP Group
With agents

Specialist reviewers on every change

Advisory agents each review a change in their own area and report what they find. They recommend; your engineers decide.

Enterprise SDLC

Enterprise SDLC discipline, built in

The playbook follows the patterns enterprise software teams rely on at every stage of the software development life cycle (SDLC). Agents work inside them, so AI-written code goes through the same controls as any other.

  • Plan

    A profile per project, and a written plan for anything non-trivial: scope, files, approach and risks, approved by a person.

  • Build

    Shared standards in every repository. Tests ship with the feature, and every bug fix adds one.

  • Review

    Specialist reviewers check security, quality, data and accessibility before a change is done.

  • Release

    Hooks block commits nobody asked for and pushes to deploy branches. Every deploy is verified where it landed.

  • Operate

    Long jobs can be stopped and resumed, report real progress and always end with a status.

  • Audit

    Every tool call logged, a daily dev log, and each incident turned into a check so it can’t recur unnoticed.

How we install it for your team

Our playbook, tailored to your teams and set up in your repositories. It plugs into Claude Code, Codex and your GitHub Enterprise workflow, so the rules travel with the code.

AI-First Engineering Teams
  1. 01

    Discover and tailor

    We learn how your teams work and what they must comply with, then amend the playbook to fit your needs and how you do business.

  2. 02

    Install

    Each repository onboarded with your version: project profile, standards, reviewer agents and guardrails, wired into GitHub Enterprise.

  3. 03

    Train

    Hands-on sessions on real work: directing agents, when to trust them, and how the reviewers keep them honest.

  4. 04

    Embed and observe

    We work beside your team on live tickets, watch what the reviewers and guardrails catch, and adjust the playbook until it sticks.

Built for enterprises, sized for any team

You don’t need a release manager or a security team to work this way. The guardrails and reviewers carry that discipline for you.

  1. Small teams

    A team of 3 works like a team of 30

    The reviewers and guardrails do the checking a dedicated QA, security and release team would, so a small team ships with the same discipline.

  2. Enterprises

    Fits the process you already have

    The patterns map onto your change management, GitHub Enterprise policies and audit needs. After discovery we amend the playbook itself to match how you work.

This website was built inside the playbook.

WakuPress, the CMS behind npgroup.net, was written by agents working within these standards and reviewers, with our engineers approving every change.

Jenna, Director of Client Services at NP Group

Jenna Director of Client Services

Want this for your team?

We install the playbook in your repositories and train your developers on real work. Talk to the engineers who use it every day.