Publish public vibecoding playbook structure (#1)

Author: XenoExia

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,15 @@
+---
+name: Bug report
+about: Report a broken link, wrong instruction, or inaccurate workflow guidance
+title: "[Bug] "
+labels: [bug]
+assignees: []
+---
+
+## What is wrong?
+
+## Where did you see it?
+
+## Why does it matter?
+
+## Suggested correction

.github/ISSUE_TEMPLATE/documentation-improvement.md

@@ -0,0 +1,13 @@
+---
+name: Documentation improvement
+about: Suggest a clearer explanation, better structure, or stronger onboarding
+title: "[Docs] "
+labels: [documentation]
+assignees: []
+---
+
+## What part of the docs needs improvement?
+
+## What is confusing or missing?
+
+## What would make it clearer?

.github/ISSUE_TEMPLATE/experience-report.md

@@ -0,0 +1,17 @@
+---
+name: Experience report
+about: Share how you adapted or used this playbook in practice
+title: "[Experience] "
+labels: [experience-report]
+assignees: []
+---
+
+## Context
+
+## Which parts of the playbook did you use?
+
+## What worked well?
+
+## What broke or felt confusing?
+
+## What should the repository document better?

.github/pull_request_template.md

@@ -0,0 +1,21 @@
+## Summary
+
+- 
+
+## Why this improves the playbook
+
+- 
+
+## Docs or structure affected
+
+- [ ] README
+- [ ] foundations docs
+- [ ] OpenCode implementation docs
+- [ ] templates or examples
+- [ ] contributor/community files
+
+## Verification
+
+- [ ] links and file paths checked
+- [ ] English and Chinese coverage considered
+- [ ] no duplicate workflow authority introduced

CHANGELOG.md

@@ -18,6 +18,22 @@ All notable workflow and documentation changes for this repository should be rec
 - improved README positioning, navigation, and adoption guidance
 - clarified private-first status and future open-source direction
 
+## 2026-03-28
+
+### Added
+
+- public-facing foundations docs for vibecoding principles, anti-patterns, verification, and case studies
+- new `docs/opencode/` implementation layer and decision record structure
+- Simplified Chinese foundations and OpenCode implementation docs
+- `LICENSE`, `SECURITY.md`, `ROADMAP.md`, and GitHub issue/PR templates
+- richer workflow-oriented prompt examples for English and Chinese readers
+
+### Changed
+
+- rewrote both README entry points around a dual-path public playbook structure
+- removed private-draft packaging from the repository landing experience
+- updated contribution guidance for public open-source collaboration
+
 ## 2026-03-22
 
 ### Documented

CONTRIBUTING.md

@@ -2,14 +2,15 @@
 
 Thanks for your interest in improving this repository.
 
-This project is currently **private-first** but intentionally structured for a future public open-source release. Contributions should preserve that direction: clarity first, composability second, novelty last.
+This project is a public playbook for AI-assisted development workflows. Contributions should preserve that direction: clarity first, composability second, novelty last.
 
 ## What this repository values
 
 - clear ownership boundaries
 - durable documentation over prompt clutter
 - reusable templates over private environment assumptions
 - bilingual parity where practical
+- evidence-backed guidance over workflow hype
 
 ## Contribution principles
 
@@ -39,7 +40,6 @@ When contributing to this repo, prefer changes that make the workflow:
 ## What is not in scope yet
 
 - screenshots or heavy visual assets without a stable story
-- public governance decisions that depend on future open-sourcing timing
 - speculative integrations that are not used in the documented stack
 
 ## Pull request expectations
@@ -50,6 +50,7 @@ Good pull requests for this repo usually:
 - keep documentation structure clean
 - avoid introducing duplicate workflow authority
 - preserve or improve bilingual parity
+- distinguish clearly between transferable methodology and OpenCode-specific implementation
 
 ## Questions to ask before opening a PR
 

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 XenoExia
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.