[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DKKTMSYVNH0FJY0RR5KQZX":3,"skill-same:01M7DKKTMSYVNH0FJY0RR5KQZX":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":40,"commitSha":41,"skillDirectory":42,"forksCount":43,"repositoryHtmlUrl":44,"repositoryHomepageUrl":6,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":46,"install":47,"resources":60},"01M7DKKTMSYVNH0FJY0RR5KQZX","geminiignore-finops",null,"Configure and optimize .geminiignore files for AI context window efficiency and token cost reduction (FinOps).","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgeminiignore-finops\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: geminiignore-finops\ndescription: \"Configure and optimize .geminiignore files for AI context window efficiency and token cost reduction (FinOps).\"\ncategory: context-optimization\nrisk: safe\nsource: community\nsource_repo: iradoweck\u002Fantigravity-awesome-skills\nsource_type: community\ndate_added: \"2026-05-25\"\nauthor: iradoweck\ntags: [finops, context-management, token-optimization, geminiignore]\ntools: [gemini, claude, cursor]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Firadoweck\u002Fantigravity-awesome-skills\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# GeminiIgnore FinOps Setup & Optimization\n\n## Overview\n\nA 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).\n\n## When to Use This Skill\n\n- Use when initializing a new repository or workspace for pair-programming with AI agents.\n- Use when the AI context window is reaching its limits or when billing optimization (FinOps) is a priority.\n- Use when the AI agent is accidentally reading build outputs, lock files, databases, or binary media.\n\n## How It Works\n\n### Step 1: Analyze the Workspace Tech Stack\nDetect the languages, frameworks, and dependency managers present in the project (e.g., Node.js, Python, PHP, Dart\u002FFlutter, Rust).\n\n### Step 2: Initialize or Update the `.geminiignore` File\nCreate a `.geminiignore` file at the root of the active workspace. If one already exists, review it to add missing categories.\n\n### Step 3: Implement the 7 Core Rules\nAdd rules divided into the following categories to filter out unnecessary machine noise while keeping human-written code visible:\n\n1. **System & Editor Noise**: Block OS temp files (`.DS_Store`, `Thumbs.db`) and user-specific IDE caches (`.idea\u002F`, `.vscode\u002F*`, Xcode user data).\n2. **Dependency Folders & Lock Files**: Ignore third-party package directories (`node_modules\u002F`, `vendor\u002F`) and giant machine-generated lock files (`package-lock.json`, `yarn.lock`, `Cargo.lock`, `composer.lock`).\n3. **Build & Target Output**: Block compiled folders (`dist\u002F`, `build\u002F`, `.next\u002F`, `.nuxt\u002F`).\n4. **Caches & Tool Metadata**: Block compiler caches (`.tsbuildinfo`, `.vite\u002F`, `.pytest_cache\u002F`, `.eslintcache`).\n5. **Binary & Rich Assets**: Block media types (`*.png`, `*.pdf`, `*.mp4`, `*.woff2`) to prevent triggering expensive vision\u002Fmultimodal tokens.\n6. **Local Databases & Logs**: Block log files (`*.log`) and SQL dumps or local SQLite DBs (`*.sqlite`, `*.db`).\n7. **Compiled Binaries & Mobile Builds**: Block mobile package files (`*.apk`, `*.ipa`) and compiled binaries (`*.class`, `*.pyc`, `*.dll`).\n\n### Step 4: Validate Exclusions\nVerify 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.\n\n## Examples\n\n### Example 1: Standard Universal `.geminiignore` Template\n\nHere is a recommended baseline configuration for a multi-language project:\n\n```ini\n# ==============================================================================\n# .geminiignore - BASELINE DE FINOPS E ARQUITETURA\n# ==============================================================================\n\n# 1. SISTEMA OPERACIONAL E IDEs\n.DS_Store\nThumbs.db\nDesktop.ini\n$RECYCLE.BIN\u002F\n.vscode\u002F*\n!.vscode\u002Fsettings.json\n!.vscode\u002Ftasks.json\n!.vscode\u002Flaunch.json\n.idea\u002F\n*.iml\n.gradle\u002F\nlocal.properties\n.history\u002F\n\n# 2. DEPENDÊNCIAS (ECONOMIA DE TOKENS EM LOCK FILES)\nnode_modules\u002F\npackage-lock.json\nyarn.lock\npnpm-lock.yaml\nvendor\u002F\ncomposer.lock\nvenv\u002F\n.venv\u002F\nenv\u002F\n.env\n.env.*\n!.env.example\npoetry.lock\nCargo.lock\npubspec.lock\n\n# 3. BUILDS E EXPORTAÇÕES\ndist\u002F\nbuild\u002F\nout\u002F\ntarget\u002F\n.next\u002F\n.nuxt\u002F\n.output\u002F\nbin\u002F\nobj\u002F\n\n# 4. CACHES DE FRAMEWORKS\n.vite\u002F\n.parcel-cache\u002F\n.eslintcache\n.babel-cache\u002F\n.tsbuildinfo\n.turbo\u002F\n.pytest_cache\u002F\n.ruff_cache\u002F\nstorage\u002Fframework\u002F\nstorage\u002Flogs\u002F\n\n# 5. ASSETS BINÁRIOS E MULTIMÍDIA EXTREMOS\n*.png\n*.jpg\n*.jpeg\n*.gif\n*.webp\n*.svg\n*.ico\n*.psd\n*.fig\n*.pdf\n*.zip\n*.tar.gz\n*.woff\n*.woff2\n*.ttf\n\n# 6. BANCOS DE DADOS E LOGS\n*.log\n*.db\n*.sqlite\n*.sqlite3\n*.sql\n*.sql.gz\n\n# 7. ARQUIVOS COMPILADOS\n*.apk\n*.aab\n*.ipa\n*.jar\n*.class\n*.pyc\n__pycache__\u002F\n*.so\n*.dylib\n*.dll\n*.exe\n*.js.map\n*.css.map\n```\n\n## Best Practices\n\n- ✅ **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.\n- ✅ **Keep configurations visible**: Ensure manifests like `package.json`, `composer.json`, `Cargo.toml`, and `pyproject.toml` are NEVER ignored, as the AI needs them to understand dependencies.\n- ✅ **Whitelist config examples**: Use rules like `!.env.example` alongside `.env` ignores so the AI understands configuration structure without exposing credentials.\n- ❌ **Do not ignore source code**: Avoid overly broad folder patterns like `lib\u002F` or `app\u002F` if they contain primary source code. Be specific (e.g., block `vendor\u002Fbundle\u002F` but not your actual code).\n\n## Limitations\n\n- A `.geminiignore` file only affects AI tools parsing the workspace; it does not replace `.gitignore` for Git repository hosting.\n- Patterns must be formatted correctly according to gitignore-style globbing to avoid accidentally ignoring source files.\n\n## Related Skills\n\n- `@context-optimization` - Broad tactics for context window management.\n- `@clean-code` - Architectural practices for clean, human-readable codebases.\n","# GeminiIgnore FinOps Setup & Optimization\n\n## Overview\n\nA 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).\n\n## When to Use This Skill\n\n- Use when initializing a new repository or workspace for pair-programming with AI agents.\n- Use when the AI context window is reaching its limits or when billing optimization (FinOps) is a priority.\n- Use when the AI agent is accidentally reading build outputs, lock files, databases, or binary media.\n\n## How It Works\n\n### Step 1: Analyze the Workspace Tech Stack\nDetect the languages, frameworks, and dependency managers present in the project (e.g., Node.js, Python, PHP, Dart\u002FFlutter, Rust).\n\n### Step 2: Initialize or Update the `.geminiignore` File\nCreate a `.geminiignore` file at the root of the active workspace. If one already exists, review it to add missing categories.\n\n### Step 3: Implement the 7 Core Rules\nAdd rules divided into the following categories to filter out unnecessary machine noise while keeping human-written code visible:\n\n1. **System & Editor Noise**: Block OS temp files (`.DS_Store`, `Thumbs.db`) and user-specific IDE caches (`.idea\u002F`, `.vscode\u002F*`, Xcode user data).\n2. **Dependency Folders & Lock Files**: Ignore third-party package directories (`node_modules\u002F`, `vendor\u002F`) and giant machine-generated lock files (`package-lock.json`, `yarn.lock`, `Cargo.lock`, `composer.lock`).\n3. **Build & Target Output**: Block compiled folders (`dist\u002F`, `build\u002F`, `.next\u002F`, `.nuxt\u002F`).\n4. **Caches & Tool Metadata**: Block compiler caches (`.tsbuildinfo`, `.vite\u002F`, `.pytest_cache\u002F`, `.eslintcache`).\n5. **Binary & Rich Assets**: Block media types (`*.png`, `*.pdf`, `*.mp4`, `*.woff2`) to prevent triggering expensive vision\u002Fmultimodal tokens.\n6. **Local Databases & Logs**: Block log files (`*.log`) and SQL dumps or local SQLite DBs (`*.sqlite`, `*.db`).\n7. **Compiled Binaries & Mobile Builds**: Block mobile package files (`*.apk`, `*.ipa`) and compiled binaries (`*.class`, `*.pyc`, `*.dll`).\n\n### Step 4: Validate Exclusions\nVerify 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.\n\n## Examples\n\n### Example 1: Standard Universal `.geminiignore` Template\n\nHere is a recommended baseline configuration for a multi-language project:\n\n```ini\n# ==============================================================================\n# .geminiignore - BASELINE DE FINOPS E ARQUITETURA\n# ==============================================================================\n\n# 1. SISTEMA OPERACIONAL E IDEs\n.DS_Store\nThumbs.db\nDesktop.ini\n$RECYCLE.BIN\u002F\n.vscode\u002F*\n!.vscode\u002Fsettings.json\n!.vscode\u002Ftasks.json\n!.vscode\u002Flaunch.json\n.idea\u002F\n*.iml\n.gradle\u002F\nlocal.properties\n.history\u002F\n\n# 2. DEPENDÊNCIAS (ECONOMIA DE TOKENS EM LOCK FILES)\nnode_modules\u002F\npackage-lock.json\nyarn.lock\npnpm-lock.yaml\nvendor\u002F\ncomposer.lock\nvenv\u002F\n.venv\u002F\nenv\u002F\n.env\n.env.*\n!.env.example\npoetry.lock\nCargo.lock\npubspec.lock\n\n# 3. BUILDS E EXPORTAÇÕES\ndist\u002F\nbuild\u002F\nout\u002F\ntarget\u002F\n.next\u002F\n.nuxt\u002F\n.output\u002F\nbin\u002F\nobj\u002F\n\n# 4. CACHES DE FRAMEWORKS\n.vite\u002F\n.parcel-cache\u002F\n.eslintcache\n.babel-cache\u002F\n.tsbuildinfo\n.turbo\u002F\n.pytest_cache\u002F\n.ruff_cache\u002F\nstorage\u002Fframework\u002F\nstorage\u002Flogs\u002F\n\n# 5. ASSETS BINÁRIOS E MULTIMÍDIA EXTREMOS\n*.png\n*.jpg\n*.jpeg\n*.gif\n*.webp\n*.svg\n*.ico\n*.psd\n*.fig\n*.pdf\n*.zip\n*.tar.gz\n*.woff\n*.woff2\n*.ttf\n\n# 6. BANCOS DE DADOS E LOGS\n*.log\n*.db\n*.sqlite\n*.sqlite3\n*.sql\n*.sql.gz\n\n# 7. ARQUIVOS COMPILADOS\n*.apk\n*.aab\n*.ipa\n*.jar\n*.class\n*.pyc\n__pycache__\u002F\n*.so\n*.dylib\n*.dll\n*.exe\n*.js.map\n*.css.map\n```\n\n## Best Practices\n\n- ✅ **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.\n- ✅ **Keep configurations visible**: Ensure manifests like `package.json`, `composer.json`, `Cargo.toml`, and `pyproject.toml` are NEVER ignored, as the AI needs them to understand dependencies.\n- ✅ **Whitelist config examples**: Use rules like `!.env.example` alongside `.env` ignores so the AI understands configuration structure without exposing credentials.\n- ❌ **Do not ignore source code**: Avoid overly broad folder patterns like `lib\u002F` or `app\u002F` if they contain primary source code. Be specific (e.g., block `vendor\u002Fbundle\u002F` but not your actual code).\n\n## Limitations\n\n- A `.geminiignore` file only affects AI tools parsing the workspace; it does not replace `.gitignore` for Git repository hosting.\n- Patterns must be formatted correctly according to gitignore-style globbing to avoid accidentally ignoring source files.\n\n## Related Skills\n\n- `@context-optimization` - Broad tactics for context window management.\n- `@clean-code` - Architectural practices for clean, human-readable codebases.\n",{"name":5,"risk":24,"tags":25,"tools":30,"author":34,"source":35,"license":15,"category":36,"date_added":37,"description":7,"source_repo":38,"source_type":35,"license_source":39},"safe",[26,27,28,29],"finops","context-management","token-optimization","geminiignore",[31,32,33],"gemini","claude","cursor","iradoweck","community","context-optimization","2026-05-25","iradoweck\u002Fantigravity-awesome-skills","https:\u002F\u002Fgithub.com\u002Firadoweck\u002Fantigravity-awesome-skills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fgeminiignore-finops",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":59},[49,52,55],{"tool":50,"command":51},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill geminiignore-finops",{"tool":53,"command":54},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill geminiignore-finops",{"tool":56,"command":57},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill geminiignore-finops","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgeminiignore-finops\u002FSKILL.md",true,[],[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]