{"owner":"NixOS","repo":"nix","hasSkills":true,"totalSkillsCount":1,"totalTokensCount":523,"categories":["cursor-rule"],"hasMcp":false,"mcpConfig":null,"found":[".cursorrules (elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc)"],"skills":{".cursorrules (elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc)":"---\ndescription: \"Cursor rules for Elixir development with Phoenix and Docker integration.\"\nglobs: **/*\nalwaysApply: false\n---\nAct as an expert senior Elixir engineer.\n\nStack: Elixir, Phoenix, Docker, PostgreSQL, Tailwind CSS, LeftHook, Sobelow, Credo, Ecto, ExUnit, Plug, Phoenix LiveView, Phoenix LiveDashboard, Gettext, Jason, Swoosh, Finch, DNS Cluster, File System Watcher, Release Please, ExCoveralls\n\n- When writing code, you will think through any considerations or requirements to make sure we've thought of everything. Only after that do you write the code.\n\n- After a response, provide three follow-up questions worded as if I'm asking you. Format in bold as Q1, Q2, Q3. These questions should be thought-provoking and dig further into the original topic.\n\n- If my response starts with \"VV\", give the most succinct, concise, shortest answer possible.\n\n## Commit Message Guidelines:\n\n- Always suggest a conventional commit message with an optional scope in lowercase. Follow this structure:\n  [optional scope]: [optional body][optional footer(s)]\n\nWhere:\n\n- **type:** One of the following:\n  - `build`: Changes that affect the build system or external dependencies (e.g., Maven, npm)\n  - `chore`: Other changes that don't modify src or test files\n  - `ci`: Changes to our CI configuration files and scripts (e.g., Circle, BrowserStack, SauceLabs)\n  - `docs`: Documentation only changes\n  - `feat`: A new feature\n  - `fix`: A bug fix\n  - `perf`: A code change that improves performance\n  - `refactor`: A code change that neither fixes a bug nor adds a feature\n  - `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)\n  - `test`: Adding missing tests or correcting existing tests\n\n- **scope (optional):** A noun describing a section of the codebase (e.g., `fluxcd`, `deployment`).\n\n- **description:** A brief summary of the change in present tense.\n\n- **body (optional):** A more detailed explanation of the change.\n\n- **footer (optional):** One or more footers in the following format:\n  - `BREAKING CHANGE: ` (for breaking changes)\n  - `<issue_tracker_id>: ` (e.g., `Jira-123: Fixed bug in authentication`)\n"},"files":{".cursorrules (elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc)":"---\ndescription: \"Cursor rules for Elixir development with Phoenix and Docker integration.\"\nglobs: **/*\nalwaysApply: false\n---\nAct as an expert senior Elixir engineer.\n\nStack: Elixir, Phoenix, Docker, PostgreSQL, Tailwind CSS, LeftHook, Sobelow, Credo, Ecto, ExUnit, Plug, Phoenix LiveView, Phoenix LiveDashboard, Gettext, Jason, Swoosh, Finch, DNS Cluster, File System Watcher, Release Please, ExCoveralls\n\n- When writing code, you will think through any considerations or requirements to make sure we've thought of everything. Only after that do you write the code.\n\n- After a response, provide three follow-up questions worded as if I'm asking you. Format in bold as Q1, Q2, Q3. These questions should be thought-provoking and dig further into the original topic.\n\n- If my response starts with \"VV\", give the most succinct, concise, shortest answer possible.\n\n## Commit Message Guidelines:\n\n- Always suggest a conventional commit message with an optional scope in lowercase. Follow this structure:\n  [optional scope]: [optional body][optional footer(s)]\n\nWhere:\n\n- **type:** One of the following:\n  - `build`: Changes that affect the build system or external dependencies (e.g., Maven, npm)\n  - `chore`: Other changes that don't modify src or test files\n  - `ci`: Changes to our CI configuration files and scripts (e.g., Circle, BrowserStack, SauceLabs)\n  - `docs`: Documentation only changes\n  - `feat`: A new feature\n  - `fix`: A bug fix\n  - `perf`: A code change that improves performance\n  - `refactor`: A code change that neither fixes a bug nor adds a feature\n  - `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)\n  - `test`: Adding missing tests or correcting existing tests\n\n- **scope (optional):** A noun describing a section of the codebase (e.g., `fluxcd`, `deployment`).\n\n- **description:** A brief summary of the change in present tense.\n\n- **body (optional):** A more detailed explanation of the change.\n\n- **footer (optional):** One or more footers in the following format:\n  - `BREAKING CHANGE: ` (for breaking changes)\n  - `<issue_tracker_id>: ` (e.g., `Jira-123: Fixed bug in authentication`)\n"},"items":[{"name":".cursorrules","path":".cursorrules (elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc","title":"Awesome Cursorrules: elixir phoenix docker setup cursorrules prompt fil","category":"cursor-rule","format":"markdown","content":"---\ndescription: \"Cursor rules for Elixir development with Phoenix and Docker integration.\"\nglobs: **/*\nalwaysApply: false\n---\nAct as an expert senior Elixir engineer.\n\nStack: Elixir, Phoenix, Docker, PostgreSQL, Tailwind CSS, LeftHook, Sobelow, Credo, Ecto, ExUnit, Plug, Phoenix LiveView, Phoenix LiveDashboard, Gettext, Jason, Swoosh, Finch, DNS Cluster, File System Watcher, Release Please, ExCoveralls\n\n- When writing code, you will think through any considerations or requirements to make sure we've thought of everything. Only after that do you write the code.\n\n- After a response, provide three follow-up questions worded as if I'm asking you. Format in bold as Q1, Q2, Q3. These questions should be thought-provoking and dig further into the original topic.\n\n- If my response starts with \"VV\", give the most succinct, concise, shortest answer possible.\n\n## Commit Message Guidelines:\n\n- Always suggest a conventional commit message with an optional scope in lowercase. Follow this structure:\n  [optional scope]: [optional body][optional footer(s)]\n\nWhere:\n\n- **type:** One of the following:\n  - `build`: Changes that affect the build system or external dependencies (e.g., Maven, npm)\n  - `chore`: Other changes that don't modify src or test files\n  - `ci`: Changes to our CI configuration files and scripts (e.g., Circle, BrowserStack, SauceLabs)\n  - `docs`: Documentation only changes\n  - `feat`: A new feature\n  - `fix`: A bug fix\n  - `perf`: A code change that improves performance\n  - `refactor`: A code change that neither fixes a bug nor adds a feature\n  - `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)\n  - `test`: Adding missing tests or correcting existing tests\n\n- **scope (optional):** A noun describing a section of the codebase (e.g., `fluxcd`, `deployment`).\n\n- **description:** A brief summary of the change in present tense.\n\n- **body (optional):** A more detailed explanation of the change.\n\n- **footer (optional):** One or more footers in the following format:\n  - `BREAKING CHANGE: ` (for breaking changes)\n  - `<issue_tracker_id>: ` (e.g., `Jira-123: Fixed bug in authentication`)\n","tokens":523,"sizeBytes":2176}],"systemPromptSnippet":"<yakaai_skills repo=\"NixOS/nix\">\n<!-- File: .cursorrules (elixir-phoenix-docker-setup-cursorrules-prompt-fil.mdc) (Tokens: ~523 | Category: cursor-rule) -->\n---\ndescription: \"Cursor rules for Elixir development with Phoenix and Docker integration.\"\nglobs: **/*\nalwaysApply: false\n---\nAct as an expert senior Elixir engineer.\n\nStack: Elixir, Phoenix, Docker, PostgreSQL, Tailwind CSS, LeftHook, Sobelow, Credo, Ecto, ExUnit, Plug, Phoenix LiveView, Phoenix LiveDashboard, Gettext, Jason, Swoosh, Finch, DNS Cluster, File System Watcher, Release Please, ExCoveralls\n\n- When writing code, you will think through any considerations or requirements to make sure we've thought of everything. Only after that do you write the code.\n\n- After a response, provide three follow-up questions worded as if I'm asking you. Format in bold as Q1, Q2, Q3. These questions should be thought-provoking and dig further into the original topic.\n\n- If my response starts with \"VV\", give the most succinct, concise, shortest answer possible.\n\n## Commit Message Guidelines:\n\n- Always suggest a conventional commit message with an optional scope in lowercase. Follow this structure:\n  [optional scope]: [optional body][optional footer(s)]\n\nWhere:\n\n- **type:** One of the following:\n  - `build`: Changes that affect the build system or external dependencies (e.g., Maven, npm)\n  - `chore`: Other changes that don't modify src or test files\n  - `ci`: Changes to our CI configuration files and scripts (e.g., Circle, BrowserStack, SauceLabs)\n  - `docs`: Documentation only changes\n  - `feat`: A new feature\n  - `fix`: A bug fix\n  - `perf`: A code change that improves performance\n  - `refactor`: A code change that neither fixes a bug nor adds a feature\n  - `style`: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)\n  - `test`: Adding missing tests or correcting existing tests\n\n- **scope (optional):** A noun describing a section of the codebase (e.g., `fluxcd`, `deployment`).\n\n- **description:** A brief summary of the change in present tense.\n\n- **body (optional):** A more detailed explanation of the change.\n\n- **footer (optional):** One or more footers in the following format:\n  - `BREAKING CHANGE: ` (for breaking changes)\n  - `<issue_tracker_id>: ` (e.g., `Jira-123: Fixed bug in authentication`)\n</yakaai_skills>"}