tekhne / bdd-testing
AGENTS.md10 starsChanged 39 days agoMITView on GitHub
Note: CLAUDE.md is a symlink to this file. Master Behavior-Driven Development (BDD) testing with comprehensive guidance on principles, patterns, Gherkin syntax, collaboration practices, and Cucumber.js implementation. Reference files are named {prefix}-{topic}.md. Principles & Philosophy (principles-): - references/principles-core-philosophy.md - What is BDD, discovery-development-delivery cycle - references/principles-three-amigos.md - Three perspectives collaboration practice - references/principles-living-documentation.md - Executable specifications as documentation - references/principles-ubiquitous-language.md - Shared vocabulary between business and tech - references/principles-example-mapping.md - Workshop technique with colored cards - references/principles-specification-by-example.md - Concrete examples drive…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository81 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/development/biome-complete/AGENTS.mdAGENTS.md
- skills/development/bun-development/AGENTS.mdAGENTS.md
- skills/development/commanderjs/AGENTS.mdAGENTS.md
- skills/documentation/markdown-authoring/AGENTS.mdAGENTS.md
- skills/package-mgmt/mise-complete/AGENTS.mdAGENTS.md
- agents-mdSkill
- cache-auditSkill
- context-radar-auditSkill
- create-contextSkill
- guided-interviewSkill
- handover-document-creatorSkill
- load-contextSkill
- pick-modelSkill
- pinSkill
- professional-honestySkill
- rules-managementSkill
- save-contextSkill
- session-reflectionSkill
- socratic-methodSkill
- vault-captureSkill
- vault-consolidateSkill
- vault-fetchSkill
- vault-searchSkill
- bird-fortune-political-satireSkill
- brooker-esque-media-satireSkill
- clarke-dawe-esqueSkill
- comedy-style-skill-generatorSkill
- cunk-esque-mockumentarySkill
- gervais-esque-cringe-satireSkill
- monty-python-esqueSkill
- pryor-esque-confessional-standupSkill
- rock-esque-observational-standupSkill
- biome-completeSkill
- bun-developmentSkill
- commanderjsSkill
- conventional-commitsSkill
- humanizerSkill
- journal-entry-importSkill
- markdown-authoringSkill
- mermaid-diagramsSkill
- plain-englishSkill
- professional-communicationSkill
- sop-structureSkill
- logql-generatorSkill
- mise-completeSkill
- context-indexSkill
- create-context-fileSkill
- follow-upSkill
- goal-trackerSkill
- nasa-pm-lessonsSkill
- plan-createSkill
- plan-executeSkill
- plan-reviewSkill
- risk-registerSkill
- tech-debtSkill
- tech-evaluationSkill
- blast-radiusSkill
- bridgeSkill
- challengeSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Read SKILL.md to understand when and how to apply BDD practices
- Distinctive: line 24
Start with principles, then move to patterns, then implementation
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
bdd-testing
Note:
CLAUDE.mdis a symlink to this file.
Overview
Master Behavior-Driven Development (BDD) testing with comprehensive guidance on principles, patterns, Gherkin syntax, collaboration practices, and Cucumber.js implementation.
Structure
bdd-testing/
SKILL.md # Main navigation hub - read this first
AGENTS.md # This file - complete reference guide
CLAUDE.md # Symlink to AGENTS.md
references/ # Detailed reference files by categoryUsage
- Read
SKILL.mdto understand when and how to apply BDD practices - Navigate to specific categories based on your current task
- Load reference files on-demand - only read what you need for the task
- Start with principles, then move to patterns, then implementation
Reference Categories
| Priority | Category | Impact | Prefix |
| 1 | Principles & Philosophy | CRITICAL | principles- |
| 2 | Gherkin Syntax & Structure | CRITICAL | gherkin- |
| 3 | Collaboration Practices | HIGH | collaboration- |
| 4 | Scenario Writing | HIGH | scenarios- |
| 5 | Patterns & Anti-patterns | MEDIUM | patterns- |
| 6 | Cucumber.js Implementation | MEDIUM | cucumber- |
Reference files are named {prefix}-{topic}.md.
Available References
Principles & Philosophy (principles-):
references/principles-core-philosophy.md- What is BDD, discovery-development-delivery cyclereferences/principles-three-amigos.md- Three perspectives collaboration practicereferences/principles-living-documentation.md- Executable specifications as documentationreferences/principles-ubiquitous-language.md- Shared vocabulary between business and techreferences/principles-example-mapping.md- Workshop technique with colored cardsreferences/principles-specification-by-example.md- Concrete examples drive developmentreferences/principles-outside-in.md- Outside-in development workflowreferences/principles-bdd-vs-tdd.md- Differences and how they complement each other
Gherkin Syntax & Structure (gherkin-):
references/gherkin-syntax.md- Feature, Scenario, Given/When/Then keywordsreferences/gherkin-given-when-then.md- Arrange-Act-Assert pattern explainedreferences/gherkin-scenario-outlines.md- Data-driven tests with Examples tablesreferences/gherkin-background.md- Common setup for all scenarios in a featurereferences/gherkin-tags.md- Organizing and filtering scenarios with tagsreferences/gherkin-data-tables.md- Passing structured data to steps
Collaboration Practices (collaboration-):
references/collaboration-three-amigos-sessions.md- Running effective discovery sessionsreferences/collaboration-example-mapping-workshop.md- Yellow/blue/green/red card techniquereferences/collaboration-discovery-workshop.md- Structured 50-minute workshop formatreferences/collaboration-building-ubiquitous-language.md- Creating shared domain vocabularyreferences/collaboration-stakeholder-involvement.md- Engaging business stakeholders
Scenario Writing (scenarios-):
references/scenarios-writing-good-scenarios.md- Specific, declarative, independent scenariosreferences/scenarios-acceptance-criteria.md- Rule-based acceptance criteria formatreferences/scenarios-edge-cases.md- Systematically covering edge casesreferences/scenarios-organization.md- Feature file structure and organizationreferences/scenarios-declarative-vs-imperative.md- Business-focused vs implementation-focused
Patterns & Anti-patterns (patterns-):
references/patterns-one-scenario-one-behavior.md- Single responsibility for scenariosreferences/patterns-independent-scenarios.md- Avoiding scenario dependenciesreferences/patterns-background-usage.md- When and how to use Backgroundreferences/patterns-reusable-steps.md- Creating maintainable step definitionsreferences/patterns-domain-language.md- Using business terms not technical jargonreferences/patterns-common-antipatterns.md- What to avoid in BDD tests
Cucumber.js Implementation (cucumber-):
references/cucumber-setup.md- Installation and project structurereferences/cucumber-step-definitions.md- Writing step definitions in TypeScriptreferences/cucumber-cucumber-expressions.md- Parameter types and custom patternsreferences/cucumber-world.md- Sharing state between stepsreferences/cucumber-hooks.md- Before/After hooks and setup/teardownreferences/cucumber-configuration.md- cucumber.js config, parallel execution, profilesreferences/cucumber-running-tests.md- CLI commands, tags, dry-run, snippets
Consolidates 6 original skills: bdd-collaboration, bdd-gherkin, bdd-patterns, bdd-principles, bdd-scenarios, cucumber-best-practices
42 reference files across 6 categories
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

