No-Slop OSS, a checklist of contribution best practices when using AI (or not)

Description and use

**Brief Summary**
No‑Slop OSS is an open‑source checklist that codifies best‑practice guidelines for contributing code that uses (or deliberately avoids) AI. It helps teams add AI capabilities—such as prototype features, Retrieval‑Augmented Generation (RAG) pipelines, or autonomous agents—without having to design a model stack from scratch.

**Value**

• **Accelerates AI prototyping** – By providing a ready‑made set of do‑and‑don’t rules, developers can focus on product logic rather than reinventing safety, testing, and documentation practices.
• **Reduces risk** – The checklist surfaces common pitfalls (data leakage, prompt injection, model‑version drift, licensing) that often lead to costly rework or compliance issues.
• **Standardises workflow** – Teams can adopt a shared “AI contribution contract,” making code reviews, CI pipelines, and governance audits more consistent across projects.

**Practical Adoption Path**

1. **Review the checklist** – Clone the repo, read the markdown files, and map each item to your existing development workflow (e.g., PR templates, CI linting).
2. **Pilot on a low‑stakes feature** – Apply the checklist to a small RAG or agent prototype; use the “manual inspection” note to verify that integration signals (e.g., model version tags, dependency pins) are present.
3. **Automate compliance** – Convert checklist items into CI checks (e.g., enforce pinned model versions, run prompt‑testing scripts, verify licensing headers).
4. **Iterate and document** – Capture any gaps (missing tooling, ambiguous steps) and contribute back improvements, ensuring the checklist stays aligned with your organization’s policies.

**Production Readiness**

• **Readiness Level: Medium** – The checklist is mature enough for internal prototypes and controlled production roll‑outs, but it lacks extensive community backing and automated enforcement tools.
• **Pre‑deployment checklist**: verify the project’s license compatibility, confirm active maintenance (issues are responded to, releases are regular), and supplement sparse metadata with your own integration tests.
• **Post‑deployment**: monitor for drift in model APIs, update the checklist as new AI safety standards emerge, and incorporate it into your formal governance process before scaling to mission‑critical services.

Use in a workflow

No-Slop OSS, a checklist of contribution best practices when using AI (or not) helps add AI capability without starting from a blank model stack.

• prototype AI features
• build RAG or agent workflows
• evaluate model tooling

Limitations and review notes

Medium: useful for prototypes or internal workflows, with dependency and maintenance checks before production.