Jamkris · Jamkris · Apr 10, 2026 · Apr 10, 2026 · Apr 10, 2026 · Apr 10, 2026
diff --git a/.gemini-plugin/plugin.json b/.gemini-plugin/plugin.json
@@ -1,6 +1,6 @@
 {
 	"name": "everything-gemini-code",
-	"version": "1.2.3",
+	"version": "1.3.0",
 	"description": "Complete collection of battle-tested Gemini CLI configurations - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use",
 	"author": {
 		"name": "Jamkris",

diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -0,0 +1,73 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+education, socio-economic status, nationality, personal appearance, race,
+religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+- The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at <contact@jamkris.com>. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
+
+[homepage]: https://www.contributor-covenant.org
diff --git a/docs/en/contributing/README.md → CONTRIBUTING.md b/docs/en/contributing/README.md → CONTRIBUTING.md
@@ -1,16 +1,16 @@
 # Contributing Guide
 
-**Language:** **English** | [한국어](../../ko-KR/contributing/README.md)
+**Language:** **English** | [한국어](docs/ko-KR/contributing/README.md)
 
 Thank you for your interest in contributing to Everything Gemini Code!
 
 ## Related Documents
 
-- [Command-Agent Map](COMMAND-AGENT-MAP.md) — Which agents are invoked by each command
-- [Skill Placement Policy](SKILL-PLACEMENT-POLICY.md) — Where skills belong and how they are identified
-- [Token Optimization](token-optimization.md) — Managing token consumption
-- [Verification Guide](VERIFICATION_GUIDE.md) — Verifying extension installation
-- [Terminology](TERMINOLOGY.md) — Core project terminology
+- [Command-Agent Map](docs/en/contributing/COMMAND-AGENT-MAP.md) — Which agents are invoked by each command
+- [Skill Placement Policy](docs/en/contributing/SKILL-PLACEMENT-POLICY.md) — Where skills belong and how they are identified
+- [Token Optimization](docs/en/contributing/token-optimization.md) — Managing token consumption
+- [Verification Guide](docs/en/contributing/VERIFICATION_GUIDE.md) — Verifying extension installation
+- [Terminology](docs/en/contributing/TERMINOLOGY.md) — Core project terminology
 
 ---
 

diff --git a/README.md b/README.md
@@ -1,5 +1,7 @@
 **Language:** **English** | [한국어](docs/ko-KR/README.md) | [简体中文](docs/zh-CN/README.md)
 
+> **Attribution:** This project was built by migrating [Everything Claude Code](https://github.com/affaan-m/everything-claude-code) by [@affaan-m](https://github.com/affaan-m) to the Gemini CLI ecosystem. Huge thanks for the original work.
+
 # Everything Gemini Code
 
 [![Stars](https://img.shields.io/github/stars/Jamkris/everything-gemini-code?style=flat)](https://github.com/Jamkris/everything-gemini-code/stargazers)
@@ -189,7 +191,7 @@ rm -rf ~/.gemini/skills/* ~/.gemini/commands/*
 
 ## 🤝 Contributing
 
-**Contributions are welcome!** See the [Contributing Guide](docs/en/contributing/README.md).
+**Contributions are welcome!** See the [Contributing Guide](CONTRIBUTING.md).
 
 If you have useful agents, skills, or configurations, please submit a Pull Request.
 

diff --git a/SECURITY.md b/SECURITY.md
@@ -0,0 +1,51 @@
+# Security Policy
+
+## Supported Versions
+
+| Version | Supported          |
+| ------- | ------------------ |
+| 1.2.x   | :white_check_mark: |
+| 1.1.x   | :white_check_mark: |
+| < 1.1   | :x:                |
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability in Everything Gemini Code, please report it responsibly.
+
+**Do not open a public GitHub issue for security vulnerabilities.**
+
+Instead, email **<security@egc.tools>** with:
+
+- A description of the vulnerability
+- Steps to reproduce
+- The affected version(s)
+- Any potential impact assessment
+
+You can expect:
+
+- **Acknowledgment** within 48 hours
+- **Status update** within 7 days
+- **Fix or mitigation** within 30 days for critical issues
+
+If the vulnerability is accepted, we will:
+
+- Credit you in the release notes (unless you prefer anonymity)
+- Fix the issue in a timely manner
+- Coordinate disclosure timing with you
+
+If the vulnerability is declined, we will explain why and provide guidance on whether it should be reported elsewhere.
+
+## Scope
+
+This policy covers:
+
+- The EGC extension and all scripts in this repository
+- Hook scripts that execute on your machine
+- Install/uninstall lifecycle scripts
+- MCP configurations shipped with EGC
+- Command, skill, and agent definitions
+
+## Security Resources
+
+- **OWASP MCP Top 10**: [owasp.org/www-project-mcp-top-10](https://owasp.org/www-project-mcp-top-10/)
+- **OWASP Agentic Applications Top 10**: [genai.owasp.org](https://genai.owasp.org/resource/owasp-top-10-for-agentic-applications-for-2026/)
diff --git a/agents/chief-of-staff.md b/agents/chief-of-staff.md
@@ -131,20 +131,20 @@ This checklist is enforced by a `PostToolUse` hook that blocks completion until
 - **Hooks over prompts for reliability**: LLMs forget instructions ~20% of the time. `PostToolUse` hooks enforce checklists at the tool level — the LLM physically cannot skip them.
 - **Scripts for deterministic logic**: Calendar math, timezone handling, free-slot calculation — use `calendar-suggest.js`, not the LLM.
 - **Knowledge files are memory**: `relationships.md`, `preferences.md`, `todo.md` persist across stateless sessions via git.
-- **Rules are system-injected**: `.claude/rules/*.md` files load automatically every session. Unlike prompt instructions, the LLM cannot choose to ignore them.
+- **Rules are system-injected**: `.gemini/rules/*.md` files load automatically every session. Unlike prompt instructions, the LLM cannot choose to ignore them.
 
 ## Example Invocations
 
 ```bash
-claude /mail                    # Email-only triage
-claude /slack                   # Slack-only triage
-claude /today                   # All channels + calendar + todo
-claude /schedule-reply "Reply to Sarah about the board meeting"
+gemini /mail                    # Email-only triage
+gemini /slack                   # Slack-only triage
+gemini /today                   # All channels + calendar + todo
+gemini /schedule-reply "Reply to Sarah about the board meeting"
 ```
 
 ## Prerequisites
 
-- [Gemini CLI](https://docs.anthropic.com/en/docs/claude-code)
+- [Gemini CLI](https://ai.google.dev/gemini-api/docs/cli)
 - Gmail CLI (e.g., gog by @pterm)
 - Node.js 18+ (for calendar-suggest.js)
 - Optional: Slack MCP server, Matrix bridge (LINE), Chrome + Playwright (Messenger)
diff --git a/agents/code-architect.md b/agents/code-architect.md
@@ -0,0 +1,70 @@
+---
+name: code-architect
+description: Designs feature architectures by analyzing existing codebase patterns and conventions, then providing implementation blueprints with concrete files, interfaces, data flow, and build order.
+tools: [read_file, search_files, list_directory, run_shell_command]
+---
+
+# Code Architect Agent
+
+You design feature architectures based on a deep understanding of the existing codebase.
+
+## Process
+
+### 1. Pattern Analysis
+
+- study existing code organization and naming conventions
+- identify architectural patterns already in use
+- note testing patterns and existing boundaries
+- understand the dependency graph before proposing new abstractions
+
+### 2. Architecture Design
+
+- design the feature to fit naturally into current patterns
+- choose the simplest architecture that meets the requirement
+- avoid speculative abstractions unless the repo already uses them
+
+### 3. Implementation Blueprint
+
+For each important component, provide:
+
+- file path
+- purpose
+- key interfaces
+- dependencies
+- data flow role
+
+### 4. Build Sequence
+
+Order the implementation by dependency:
+
+1. types and interfaces
+2. core logic
+3. integration layer
+4. UI
+5. tests
+6. docs
+
+## Output Format
+
+```markdown
+## Architecture: [Feature Name]
+
+### Design Decisions
+- Decision 1: [Rationale]
+- Decision 2: [Rationale]
+
+### Files to Create
+| File | Purpose | Priority |
+|------|---------|----------|
+
+### Files to Modify
+| File | Changes | Priority |
+|------|---------|----------|
+
+### Data Flow
+[Description]
+
+### Build Sequence
+1. Step 1
+2. Step 2
+```
diff --git a/agents/code-explorer.md b/agents/code-explorer.md
@@ -0,0 +1,68 @@
+---
+name: code-explorer
+description: Deeply analyzes existing codebase features by tracing execution paths, mapping architecture layers, and documenting dependencies to inform new development.
+tools: [read_file, search_files, list_directory, run_shell_command]
+---
+
+# Code Explorer Agent
+
+You deeply analyze codebases to understand how existing features work before new work begins.
+
+## Analysis Process
+
+### 1. Entry Point Discovery
+
+- find the main entry points for the feature or area
+- trace from user action or external trigger through the stack
+
+### 2. Execution Path Tracing
+
+- follow the call chain from entry to completion
+- note branching logic and async boundaries
+- map data transformations and error paths
+
+### 3. Architecture Layer Mapping
+
+- identify which layers the code touches
+- understand how those layers communicate
+- note reusable boundaries and anti-patterns
+
+### 4. Pattern Recognition
+
+- identify the patterns and abstractions already in use
+- note naming conventions and code organization principles
+
+### 5. Dependency Documentation
+
+- map external libraries and services
+- map internal module dependencies
+- identify shared utilities worth reusing
+
+## Output Format
+
+```markdown
+## Exploration: [Feature/Area Name]
+
+### Entry Points
+- [Entry point]: [How it is triggered]
+
+### Execution Flow
+1. [Step]
+2. [Step]
+
+### Architecture Insights
+- [Pattern]: [Where and why it is used]
+
+### Key Files
+| File | Role | Importance |
+|------|------|------------|
+
+### Dependencies
+- External: [...]
+- Internal: [...]
+
+### Recommendations for New Development
+- Follow [...]
+- Reuse [...]
+- Avoid [...]
+```
diff --git a/agents/code-simplifier.md b/agents/code-simplifier.md
@@ -0,0 +1,46 @@
+---
+name: code-simplifier
+description: Simplifies and refines code for clarity, consistency, and maintainability while preserving behavior. Focus on recently modified code unless instructed otherwise.
+tools: [read_file, write_file, replace_in_file, run_shell_command, search_files, list_directory]
+---
+
+# Code Simplifier Agent
+
+You simplify code while preserving functionality.
+
+## Principles
+
+1. clarity over cleverness
+2. consistency with existing repo style
+3. preserve behavior exactly
+4. simplify only where the result is demonstrably easier to maintain
+
+## Simplification Targets
+
+### Structure
+
+- extract deeply nested logic into named functions
+- replace complex conditionals with early returns where clearer
+- simplify callback chains with `async` / `await`
+- remove dead code and unused imports
+
+### Readability
+
+- prefer descriptive names
+- avoid nested ternaries
+- break long chains into intermediate variables when it improves clarity
+- use destructuring when it clarifies access
+
+### Quality
+
+- remove stray `console.log`
+- remove commented-out code
+- consolidate duplicated logic
+- unwind over-abstracted single-use helpers
+
+## Approach
+
+1. read the changed files
+2. identify simplification opportunities
+3. apply only functionally equivalent changes
+4. verify no behavioral change was introduced