geminiignore-finops
Configure and optimize .geminiignore files for AI context window efficiency and token cost reduction (FinOps).
- License 许可
- MIT
- 最近更新
- 2026-06-13
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- geminiignore-finops
- risk
- safe
- tags
- [ "finops", "context-management", "token-optimization", "geminiignore" ]
- tools
- [ "gemini", "claude", "cursor" ]
- author
- iradoweck
- source
- community
- license
- MIT
- category
- context-optimization
- date_added
- 2026-05-25
- description
- Configure and optimize .geminiignore files for AI context window efficiency and token cost reduction (FinOps).
- source_repo
- iradoweck/antigravity-awesome-skills
- source_type
- community
- license_source
- https://github.com/iradoweck/antigravity-awesome-skills/blob/main/LICENSE
03 SKILL.md 正文
GeminiIgnore FinOps Setup & Optimization
Overview
A skill to construct, refine, and maintain high-performance .geminiignore files across diverse tech stacks. By filtering out machine-generated code, heavy logs, package locks, and binary assets, this skill optimizes the AI agent's context window, accelerates processing speed, and reduces token consumption costs (FinOps).
When to Use This Skill
- Use when initializing a new repository or workspace for pair-programming with AI agents.
- Use when the AI context window is reaching its limits or when billing optimization (FinOps) is a priority.
- Use when the AI agent is accidentally reading build outputs, lock files, databases, or binary media.
How It Works
Step 1: Analyze the Workspace Tech Stack
Detect the languages, frameworks, and dependency managers present in the project (e.g., Node.js, Python, PHP, Dart/Flutter, Rust).
Step 2: Initialize or Update the .geminiignore File
Create a .geminiignore file at the root of the active workspace. If one already exists, review it to add missing categories.
Step 3: Implement the 7 Core Rules
Add rules divided into the following categories to filter out unnecessary machine noise while keeping human-written code visible:
- System & Editor Noise: Block OS temp files (
.DS_Store,Thumbs.db) and user-specific IDE caches (.idea/,.vscode/*, Xcode user data). - Dependency Folders & Lock Files: Ignore third-party package directories (
node_modules/,vendor/) and giant machine-generated lock files (package-lock.json,yarn.lock,Cargo.lock,composer.lock). - Build & Target Output: Block compiled folders (
dist/,build/,.next/,.nuxt/). - Caches & Tool Metadata: Block compiler caches (
.tsbuildinfo,.vite/,.pytest_cache/,.eslintcache). - Binary & Rich Assets: Block media types (
*.png,*.pdf,*.mp4,*.woff2) to prevent triggering expensive vision/multimodal tokens. - Local Databases & Logs: Block log files (
*.log) and SQL dumps or local SQLite DBs (*.sqlite,*.db). - Compiled Binaries & Mobile Builds: Block mobile package files (
*.apk,*.ipa) and compiled binaries (*.class,*.pyc,*.dll).
Step 4: Validate Exclusions
Verify that the AI can still see critical configuration blueprints (like .env.example, package.json, composer.json, pyproject.toml) but ignores the actual .env files and compilation artifacts.
Examples
Example 1: Standard Universal .geminiignore Template
Here is a recommended baseline configuration for a multi-language project:
# ==============================================================================
# .geminiignore - BASELINE DE FINOPS E ARQUITETURA
# ==============================================================================
# 1. SISTEMA OPERACIONAL E IDEs
.DS_Store
Thumbs.db
Desktop.ini
$RECYCLE.BIN/
.vscode/*
!.vscode/settings.json
!.vscode/tasks.json
!.vscode/launch.json
.idea/
*.iml
.gradle/
local.properties
.history/
# 2. DEPENDÊNCIAS (ECONOMIA DE TOKENS EM LOCK FILES)
node_modules/
package-lock.json
yarn.lock
pnpm-lock.yaml
vendor/
composer.lock
venv/
.venv/
env/
.env
.env.*
!.env.example
poetry.lock
Cargo.lock
pubspec.lock
# 3. BUILDS E EXPORTAÇÕES
dist/
build/
out/
target/
.next/
.nuxt/
.output/
bin/
obj/
# 4. CACHES DE FRAMEWORKS
.vite/
.parcel-cache/
.eslintcache
.babel-cache/
.tsbuildinfo
.turbo/
.pytest_cache/
.ruff_cache/
storage/framework/
storage/logs/
# 5. ASSETS BINÁRIOS E MULTIMÍDIA EXTREMOS
*.png
*.jpg
*.jpeg
*.gif
*.webp
*.svg
*.ico
*.psd
*.fig
*.pdf
*.zip
*.tar.gz
*.woff
*.woff2
*.ttf
# 6. BANCOS DE DADOS E LOGS
*.log
*.db
*.sqlite
*.sqlite3
*.sql
*.sql.gz
# 7. ARQUIVOS COMPILADOS
*.apk
*.aab
*.ipa
*.jar
*.class
*.pyc
__pycache__/
*.so
*.dylib
*.dll
*.exe
*.js.map
*.css.map
Best Practices
- ✅ Ignore dependency lock files: Standard lock files (e.g.,
package-lock.json,yarn.lock) contain thousands of lines of redundant package resolution trees. Ignoring them is the single largest FinOps win. - ✅ Keep configurations visible: Ensure manifests like
package.json,composer.json,Cargo.toml, andpyproject.tomlare NEVER ignored, as the AI needs them to understand dependencies. - ✅ Whitelist config examples: Use rules like
!.env.examplealongside.envignores so the AI understands configuration structure without exposing credentials. - ❌ Do not ignore source code: Avoid overly broad folder patterns like
lib/orapp/if they contain primary source code. Be specific (e.g., blockvendor/bundle/but not your actual code).
Limitations
- A
.geminiignorefile only affects AI tools parsing the workspace; it does not replace.gitignorefor Git repository hosting. - Patterns must be formatted correctly according to gitignore-style globbing to avoid accidentally ignoring source files.
Related Skills
@context-optimization- Broad tactics for context window management.@clean-code- Architectural practices for clean, human-readable codebases.
04 同仓库更多 Skills
youtube-full
Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private/age-restricted videos.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
write-a-skill
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.
workflow-builder
Design and write deterministic multi-agent workflow scripts (.js files in .claude/workflows/) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.
webinar-marketing
When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar/event motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).
vpe-advisor
VP of Engineering advisory for startups: delivery throughput (DORA 4 metrics + bottleneck identification), engineering hiring funnel (sourcing → screen → onsite → offer conversion + time-to-fill + pipeline gap), engineering team structure (squad/tribe/chapter design + tech-lead manager-trigger thresholds), and production discipline (on-call, deployment cadence, postmortem culture). Use when sprint velocity is dropping, eng hiring is broken, team structure is unclear, or deciding when to add a tech-lead manager. NOT a CTO skill (which owns architecture) — VPE owns delivery operations and how the team ships.