Closing the intent-to-code chasm - specification-driven development with BDD verification chain
Overall
score
96%
Does it follow best practices?
Validation for skill structure
Common patterns for various ignore files by technology stack.
git rev-parse --git-dir 2>/dev/null -> create/verify .gitignore.dockerignore.eslintignoreignores entries cover required patterns.prettierignore.npmignore (if publishing).terraformignore.helmignorenode_modules/
dist/
build/
*.log
.env*__pycache__/
*.pyc
.venv/
venv/
dist/
*.egg-info/target/
*.class
*.jar
.gradle/
build/bin/
obj/
*.user
*.suo
packages/*.exe
*.test
vendor/
*.outtarget/
debug/
release/
*.rs.bk.DS_Store
Thumbs.db
*.tmp
*.swp
.vscode/
.idea/Install with Tessl CLI
npx tessl i tessl-labs/intent-integrity-kit@2.3.5rules
skills
iikit-00-constitution
scripts
iikit-01-specify
iikit-02-clarify
iikit-03-plan
iikit-04-checklist
scripts
dashboard
iikit-05-testify
iikit-06-tasks
iikit-07-analyze
iikit-08-implement
iikit-09-taskstoissues
iikit-bugfix
scripts
iikit-core
scripts
bash
dashboard
powershell