[ { "path": ".claude-plugin/marketplace.json", "content": "{\n \"name\": \"daily.dev\",\n \"owner\": {\n \"name\": \"daily.dev\",\n \"email\": \"support@daily.dev\"\n },\n \"metadata\": {\n \"description\": \"Official daily.dev plugins for Claude Code\",\n \"version\": \"0.4.0\"\n },\n \"plugins\": [\n {\n \"name\": \"daily.dev\",\n \"source\": \"./.claude-plugin/plugins/daily.dev\",\n \"description\": \"Overcome LLM knowledge cutoffs with real-time developer content. daily.dev aggregates articles from thousands of sources, validated by community engagement, with structured taxonomy for precise discovery.\",\n \"version\": \"0.4.0\",\n \"author\": {\n \"name\": \"daily.dev\"\n },\n \"homepage\": \"https://daily.dev\",\n \"license\": \"MIT\",\n \"keywords\": [\"daily.dev\", \"api\", \"developer\", \"content\", \"feed\", \"dailydotdev\"],\n \"category\": \"productivity\"\n },\n {\n \"name\": \"daily-dev-ask\",\n \"source\": \"./.claude-plugin/plugins/daily.dev\",\n \"description\": \"Answer technical questions using daily.dev's knowledge base. Searches articles from the developer community and synthesizes answers with source links.\",\n \"version\": \"0.4.0\",\n \"author\": {\n \"name\": \"daily.dev\"\n },\n \"homepage\": \"https://daily.dev\",\n \"license\": \"MIT\",\n \"keywords\": [\"daily.dev\", \"ask\", \"search\", \"developer\", \"articles\", \"knowledge-base\", \"dailydotdev\"],\n \"category\": \"productivity\"\n }\n ]\n}\n" }, { "path": ".claude-plugin/plugins/daily.dev/.claude-plugin/plugin.json", "content": "{\n \"name\": \"daily.dev\",\n \"description\": \"Access personalized developer content feeds from daily.dev - the professional network for developers. Surface relevant articles, tutorials, and discussions based on user interests.\",\n \"version\": \"0.4.0\"\n}\n" }, { "path": ".github/ISSUE_TEMPLATE/---bug-report.yml", "content": "name: \"🐛 Bug Report\"\ndescription: I would like to report a bug.\ntitle: \"🐛 BUG: \"\nlabels: [\n \"Type: Bug\"\n]\nbody:\n - type: markdown\n attributes:\n value: |\n - Thank you for using daily.dev and taking the time to report a bug! 😄 \n - Please try to spend some time to understand the bug and reproduce it.\n - Take a look at our template and try to add as much detail as possible.\n - The more details we have, easier it would be to fix it. \n - If any heading is not applicable, put `NA`\n - For additional information, write it in additional context.\n - type: textarea\n id: something_wrong\n attributes:\n label: \"What went wrong? 🤔\"\n description: |\n - Please provide a detailed description of the issue you encountered. Be clear and concise in explaining what is not working as expected.\n placeholder: Please describe the issue you experienced in detail, including any relevant information or context.\n validations:\n required: true\n - type: textarea\n id: expected_behavior\n attributes:\n label: \"Expected Behavior\"\n description: Please describe how you expected the system to behave when you encountered the issue.\n placeholder: Please describe the behavior that you expected to see when encountering the issue.\n - type: textarea\n id: reproduction_steps\n attributes:\n label: \"Steps to Reproduce Issue\"\n description: If possible, please share the steps to reproduce the issue.\n value: |\n 1. Go to '...'\n 2. Click on '....'\n 3. Scroll down to '....'\n 4. See the error\n render: bash\n - type: textarea\n id: solution_proposed\n attributes:\n label: \"Solution Proposed\"\n description: If you have any ideas or suggestions for how to fix the issue you encountered, please provide them in this section.\n placeholder: Please describe any potential solutions or ideas you may have for fixing the issue.\n - type: input\n id: screenshot\n attributes:\n label: \"Screenshots\"\n description: If applicable, add screenshots to help explain your problem.\n placeholder: |\n ![DESCRIPTION](LINK.png)\n validations:\n required: false\n - type: input\n id: environment\n attributes:\n label: \"Environment\"\n description: You can specify your operating system and version, web browser and version, or any other software that may be related to the issue.\n placeholder: ex. Windows 10, Chrome 91.0.4472.124\n validations:\n required: false\n - type: dropdown\n id: browsers\n attributes:\n label: \"Browsers\"\n description: What browser(s) are you seeing the problem on?\n multiple: true\n options:\n - Chrome\n - Firefox\n - Safari\n - Microsoft Edge\n - Opera\n - Brave\n - Other\n validations:\n required: false\n - type: dropdown\n id: os\n attributes:\n label: \"OS\"\n description: Please select the operating system(s) on which you are experiencing the issue from the dropdown list provided.\n multiple: true\n options:\n - Windows\n - Linux\n - Mac\n - iOS\n - Android\n - Other\n validations:\n required: false\n - type: input\n id: version_daily\n attributes:\n label: \"Version of daily.dev\"\n description: Please provide the version number of daily.dev you are using (if applicable) in the text field provided. This can help developers determine if the issue has already been solved in a newer version of the software.\n placeholder: ex. 10.1.2\n validations:\n required: false\n - type: textarea\n id: additional_context\n attributes:\n label: \"Additional Context\"\n description: If you have any additional context or information that may help us understand the problem better, please provide it here.\n placeholder: This can include any relevant logs, error messages, or other information that may be useful in diagnosing the issue.\n render: bash\n validations:\n required: false\n - type: checkboxes\n id: terms\n attributes:\n label: Code of Conduct\n description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/dailydotdev/.github/blob/master/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/dailydotdev/.github/blob/master/CONTRIBUTING.md)\n options:\n - label: I follow the conditions of this project.\n required: true\n - type: markdown\n attributes:\n value: Thank you for taking the time to report the issue! 😄 We appreciate your help! 😄 \n" }, { "path": ".github/ISSUE_TEMPLATE/---feature-request.yaml", "content": "name: \"🧩 Feature Request\"\ndescription: I would like to request a feature.\ntitle: \"🧩 FEATURE REQUEST: \"\nlabels: [\n \"Type: Feature\"\n]\nbody:\n - type: markdown\n attributes:\n value: |\n - Thank you for using daily.dev and taking time to request a feature.\n - Please try to spend some time to clearly speculate on the feature you need.\n - Take a look at our template and try to add as much detail as possible.\n - The more details we have, easier it would be to fix it. \n - If any heading is not applicable, put `NA`.\n - For additional information, write it in additional context.\n - type: input\n id: concise_title\n attributes:\n label: \"Concise Description\"\n placeholder: Enter a concise and appropriate one-line description of your feature request.\n validations:\n required: false\n - type: textarea\n id: description_feature\n attributes:\n label: \"Description\"\n description: Please describe the new functionality you would like to see added to daily.dev in a clear and detailed manner.\n placeholder: Please enter your detailed description of the new feature request here. \n validations:\n required: true\n - type: textarea\n id: feature_solution_proposed\n attributes:\n label: \"Solution Proposed\"\n description: A precise description of how you would like to see this functionality implemented.\n placeholder: Including any relevant materials such as sketches, wireframes, or flowcharts to illustrate your proposal is highly welcomed.\n - type: textarea\n id: additional_context_feature\n attributes:\n label: \"Additional Context\"\n description: If you have any additional context or information that may help us understand the problem better, please provide it here.\n placeholder: This can include any relevant logs, error messages, or other information that may be useful in diagnosing the issue.\n render: bash\n validations:\n required: false\n - type: checkboxes\n id: terms\n attributes:\n label: Code of Conduct\n description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/dailydotdev/.github/blob/master/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/dailydotdev/.github/blob/master/CONTRIBUTING.md)\n options:\n - label: I follow the conditions of this project.\n required: true\n - type: markdown\n attributes:\n value: Thank you for taking the time to suggest a feature request! Your input is greatly appreciated.\n" }, { "path": ".github/workflows/close-inactive-tickets.yml", "content": "name: Close inactive issues\non:\n schedule:\n - cron: \"30 1 * * *\"\n\njobs:\n close-issues:\n runs-on: ubuntu-latest\n permissions:\n issues: write\n steps:\n - uses: actions/stale@v5\n with:\n days-before-issue-stale: 30\n days-before-issue-close: 14\n stale-issue-label: \"stale\"\n stale-issue-message: \"This issue is stale because it has been open for 30 days with no activity.\"\n close-issue-message: \"This issue was closed because it has been inactive for 14 days since being marked as stale.\"\n repo-token: ${{ secrets.GITHUB_TOKEN }}\n exempt-issue-labels: \"Status: Accepted\"\n" }, { "path": ".gitignore", "content": ".idea/.DS_Store\n" }, { "path": "LICENSE", "content": " GNU AFFERO GENERAL PUBLIC LICENSE\n Version 3, 19 November 2007\n\n Copyright (C) 2007 Free Software Foundation, Inc. \n Everyone is permitted to copy and distribute verbatim copies\n of this license document, but changing it is not allowed.\n\n Preamble\n\n The GNU Affero General Public License is a free, copyleft license for\nsoftware and other kinds of works, specifically designed to ensure\ncooperation with the community in the case of network server software.\n\n The licenses for most software and other practical works are designed\nto take away your freedom to share and change the works. By contrast,\nour General Public Licenses are intended to guarantee your freedom to\nshare and change all versions of a program--to make sure it remains free\nsoftware for all its users.\n\n When we speak of free software, we are referring to freedom, not\nprice. Our General Public Licenses are designed to make sure that you\nhave the freedom to distribute copies of free software (and charge for\nthem if you wish), that you receive source code or can get it if you\nwant it, that you can change the software or use pieces of it in new\nfree programs, and that you know you can do these things.\n\n Developers that use our General Public Licenses protect your rights\nwith two steps: (1) assert copyright on the software, and (2) offer\nyou this License which gives you legal permission to copy, distribute\nand/or modify the software.\n\n A secondary benefit of defending all users' freedom is that\nimprovements made in alternate versions of the program, if they\nreceive widespread use, become available for other developers to\nincorporate. Many developers of free software are heartened and\nencouraged by the resulting cooperation. However, in the case of\nsoftware used on network servers, this result may fail to come about.\nThe GNU General Public License permits making a modified version and\nletting the public access it on a server without ever releasing its\nsource code to the public.\n\n The GNU Affero General Public License is designed specifically to\nensure that, in such cases, the modified source code becomes available\nto the community. It requires the operator of a network server to\nprovide the source code of the modified version running there to the\nusers of that server. Therefore, public use of a modified version, on\na publicly accessible server, gives the public access to the source\ncode of the modified version.\n\n An older license, called the Affero General Public License and\npublished by Affero, was designed to accomplish similar goals. This is\na different license, not a version of the Affero GPL, but Affero has\nreleased a new version of the Affero GPL which permits relicensing under\nthis license.\n\n The precise terms and conditions for copying, distribution and\nmodification follow.\n\n TERMS AND CONDITIONS\n\n 0. Definitions.\n\n \"This License\" refers to version 3 of the GNU Affero General Public License.\n\n \"Copyright\" also means copyright-like laws that apply to other kinds of\nworks, such as semiconductor masks.\n\n \"The Program\" refers to any copyrightable work licensed under this\nLicense. Each licensee is addressed as \"you\". \"Licensees\" and\n\"recipients\" may be individuals or organizations.\n\n To \"modify\" a work means to copy from or adapt all or part of the work\nin a fashion requiring copyright permission, other than the making of an\nexact copy. The resulting work is called a \"modified version\" of the\nearlier work or a work \"based on\" the earlier work.\n\n A \"covered work\" means either the unmodified Program or a work based\non the Program.\n\n To \"propagate\" a work means to do anything with it that, without\npermission, would make you directly or secondarily liable for\ninfringement under applicable copyright law, except executing it on a\ncomputer or modifying a private copy. Propagation includes copying,\ndistribution (with or without modification), making available to the\npublic, and in some countries other activities as well.\n\n To \"convey\" a work means any kind of propagation that enables other\nparties to make or receive copies. Mere interaction with a user through\na computer network, with no transfer of a copy, is not conveying.\n\n An interactive user interface displays \"Appropriate Legal Notices\"\nto the extent that it includes a convenient and prominently visible\nfeature that (1) displays an appropriate copyright notice, and (2)\ntells the user that there is no warranty for the work (except to the\nextent that warranties are provided), that licensees may convey the\nwork under this License, and how to view a copy of this License. If\nthe interface presents a list of user commands or options, such as a\nmenu, a prominent item in the list meets this criterion.\n\n 1. Source Code.\n\n The \"source code\" for a work means the preferred form of the work\nfor making modifications to it. \"Object code\" means any non-source\nform of a work.\n\n A \"Standard Interface\" means an interface that either is an official\nstandard defined by a recognized standards body, or, in the case of\ninterfaces specified for a particular programming language, one that\nis widely used among developers working in that language.\n\n The \"System Libraries\" of an executable work include anything, other\nthan the work as a whole, that (a) is included in the normal form of\npackaging a Major Component, but which is not part of that Major\nComponent, and (b) serves only to enable use of the work with that\nMajor Component, or to implement a Standard Interface for which an\nimplementation is available to the public in source code form. A\n\"Major Component\", in this context, means a major essential component\n(kernel, window system, and so on) of the specific operating system\n(if any) on which the executable work runs, or a compiler used to\nproduce the work, or an object code interpreter used to run it.\n\n The \"Corresponding Source\" for a work in object code form means all\nthe source code needed to generate, install, and (for an executable\nwork) run the object code and to modify the work, including scripts to\ncontrol those activities. However, it does not include the work's\nSystem Libraries, or general-purpose tools or generally available free\nprograms which are used unmodified in performing those activities but\nwhich are not part of the work. For example, Corresponding Source\nincludes interface definition files associated with source files for\nthe work, and the source code for shared libraries and dynamically\nlinked subprograms that the work is specifically designed to require,\nsuch as by intimate data communication or control flow between those\nsubprograms and other parts of the work.\n\n The Corresponding Source need not include anything that users\ncan regenerate automatically from other parts of the Corresponding\nSource.\n\n The Corresponding Source for a work in source code form is that\nsame work.\n\n 2. Basic Permissions.\n\n All rights granted under this License are granted for the term of\ncopyright on the Program, and are irrevocable provided the stated\nconditions are met. This License explicitly affirms your unlimited\npermission to run the unmodified Program. The output from running a\ncovered work is covered by this License only if the output, given its\ncontent, constitutes a covered work. This License acknowledges your\nrights of fair use or other equivalent, as provided by copyright law.\n\n You may make, run and propagate covered works that you do not\nconvey, without conditions so long as your license otherwise remains\nin force. You may convey covered works to others for the sole purpose\nof having them make modifications exclusively for you, or provide you\nwith facilities for running those works, provided that you comply with\nthe terms of this License in conveying all material for which you do\nnot control copyright. Those thus making or running the covered works\nfor you must do so exclusively on your behalf, under your direction\nand control, on terms that prohibit them from making any copies of\nyour copyrighted material outside their relationship with you.\n\n Conveying under any other circumstances is permitted solely under\nthe conditions stated below. Sublicensing is not allowed; section 10\nmakes it unnecessary.\n\n 3. Protecting Users' Legal Rights From Anti-Circumvention Law.\n\n No covered work shall be deemed part of an effective technological\nmeasure under any applicable law fulfilling obligations under article\n11 of the WIPO copyright treaty adopted on 20 December 1996, or\nsimilar laws prohibiting or restricting circumvention of such\nmeasures.\n\n When you convey a covered work, you waive any legal power to forbid\ncircumvention of technological measures to the extent such circumvention\nis effected by exercising rights under this License with respect to\nthe covered work, and you disclaim any intention to limit operation or\nmodification of the work as a means of enforcing, against the work's\nusers, your or third parties' legal rights to forbid circumvention of\ntechnological measures.\n\n 4. Conveying Verbatim Copies.\n\n You may convey verbatim copies of the Program's source code as you\nreceive it, in any medium, provided that you conspicuously and\nappropriately publish on each copy an appropriate copyright notice;\nkeep intact all notices stating that this License and any\nnon-permissive terms added in accord with section 7 apply to the code;\nkeep intact all notices of the absence of any warranty; and give all\nrecipients a copy of this License along with the Program.\n\n You may charge any price or no price for each copy that you convey,\nand you may offer support or warranty protection for a fee.\n\n 5. Conveying Modified Source Versions.\n\n You may convey a work based on the Program, or the modifications to\nproduce it from the Program, in the form of source code under the\nterms of section 4, provided that you also meet all of these conditions:\n\n a) The work must carry prominent notices stating that you modified\n it, and giving a relevant date.\n\n b) The work must carry prominent notices stating that it is\n released under this License and any conditions added under section\n 7. This requirement modifies the requirement in section 4 to\n \"keep intact all notices\".\n\n c) You must license the entire work, as a whole, under this\n License to anyone who comes into possession of a copy. This\n License will therefore apply, along with any applicable section 7\n additional terms, to the whole of the work, and all its parts,\n regardless of how they are packaged. This License gives no\n permission to license the work in any other way, but it does not\n invalidate such permission if you have separately received it.\n\n d) If the work has interactive user interfaces, each must display\n Appropriate Legal Notices; however, if the Program has interactive\n interfaces that do not display Appropriate Legal Notices, your\n work need not make them do so.\n\n A compilation of a covered work with other separate and independent\nworks, which are not by their nature extensions of the covered work,\nand which are not combined with it such as to form a larger program,\nin or on a volume of a storage or distribution medium, is called an\n\"aggregate\" if the compilation and its resulting copyright are not\nused to limit the access or legal rights of the compilation's users\nbeyond what the individual works permit. Inclusion of a covered work\nin an aggregate does not cause this License to apply to the other\nparts of the aggregate.\n\n 6. Conveying Non-Source Forms.\n\n You may convey a covered work in object code form under the terms\nof sections 4 and 5, provided that you also convey the\nmachine-readable Corresponding Source under the terms of this License,\nin one of these ways:\n\n a) Convey the object code in, or embodied in, a physical product\n (including a physical distribution medium), accompanied by the\n Corresponding Source fixed on a durable physical medium\n customarily used for software interchange.\n\n b) Convey the object code in, or embodied in, a physical product\n (including a physical distribution medium), accompanied by a\n written offer, valid for at least three years and valid for as\n long as you offer spare parts or customer support for that product\n model, to give anyone who possesses the object code either (1) a\n copy of the Corresponding Source for all the software in the\n product that is covered by this License, on a durable physical\n medium customarily used for software interchange, for a price no\n more than your reasonable cost of physically performing this\n conveying of source, or (2) access to copy the\n Corresponding Source from a network server at no charge.\n\n c) Convey individual copies of the object code with a copy of the\n written offer to provide the Corresponding Source. This\n alternative is allowed only occasionally and noncommercially, and\n only if you received the object code with such an offer, in accord\n with subsection 6b.\n\n d) Convey the object code by offering access from a designated\n place (gratis or for a charge), and offer equivalent access to the\n Corresponding Source in the same way through the same place at no\n further charge. You need not require recipients to copy the\n Corresponding Source along with the object code. If the place to\n copy the object code is a network server, the Corresponding Source\n may be on a different server (operated by you or a third party)\n that supports equivalent copying facilities, provided you maintain\n clear directions next to the object code saying where to find the\n Corresponding Source. Regardless of what server hosts the\n Corresponding Source, you remain obligated to ensure that it is\n available for as long as needed to satisfy these requirements.\n\n e) Convey the object code using peer-to-peer transmission, provided\n you inform other peers where the object code and Corresponding\n Source of the work are being offered to the general public at no\n charge under subsection 6d.\n\n A separable portion of the object code, whose source code is excluded\nfrom the Corresponding Source as a System Library, need not be\nincluded in conveying the object code work.\n\n A \"User Product\" is either (1) a \"consumer product\", which means any\ntangible personal property which is normally used for personal, family,\nor household purposes, or (2) anything designed or sold for incorporation\ninto a dwelling. In determining whether a product is a consumer product,\ndoubtful cases shall be resolved in favor of coverage. For a particular\nproduct received by a particular user, \"normally used\" refers to a\ntypical or common use of that class of product, regardless of the status\nof the particular user or of the way in which the particular user\nactually uses, or expects or is expected to use, the product. A product\nis a consumer product regardless of whether the product has substantial\ncommercial, industrial or non-consumer uses, unless such uses represent\nthe only significant mode of use of the product.\n\n \"Installation Information\" for a User Product means any methods,\nprocedures, authorization keys, or other information required to install\nand execute modified versions of a covered work in that User Product from\na modified version of its Corresponding Source. The information must\nsuffice to ensure that the continued functioning of the modified object\ncode is in no case prevented or interfered with solely because\nmodification has been made.\n\n If you convey an object code work under this section in, or with, or\nspecifically for use in, a User Product, and the conveying occurs as\npart of a transaction in which the right of possession and use of the\nUser Product is transferred to the recipient in perpetuity or for a\nfixed term (regardless of how the transaction is characterized), the\nCorresponding Source conveyed under this section must be accompanied\nby the Installation Information. But this requirement does not apply\nif neither you nor any third party retains the ability to install\nmodified object code on the User Product (for example, the work has\nbeen installed in ROM).\n\n The requirement to provide Installation Information does not include a\nrequirement to continue to provide support service, warranty, or updates\nfor a work that has been modified or installed by the recipient, or for\nthe User Product in which it has been modified or installed. Access to a\nnetwork may be denied when the modification itself materially and\nadversely affects the operation of the network or violates the rules and\nprotocols for communication across the network.\n\n Corresponding Source conveyed, and Installation Information provided,\nin accord with this section must be in a format that is publicly\ndocumented (and with an implementation available to the public in\nsource code form), and must require no special password or key for\nunpacking, reading or copying.\n\n 7. Additional Terms.\n\n \"Additional permissions\" are terms that supplement the terms of this\nLicense by making exceptions from one or more of its conditions.\nAdditional permissions that are applicable to the entire Program shall\nbe treated as though they were included in this License, to the extent\nthat they are valid under applicable law. If additional permissions\napply only to part of the Program, that part may be used separately\nunder those permissions, but the entire Program remains governed by\nthis License without regard to the additional permissions.\n\n When you convey a copy of a covered work, you may at your option\nremove any additional permissions from that copy, or from any part of\nit. (Additional permissions may be written to require their own\nremoval in certain cases when you modify the work.) You may place\nadditional permissions on material, added by you to a covered work,\nfor which you have or can give appropriate copyright permission.\n\n Notwithstanding any other provision of this License, for material you\nadd to a covered work, you may (if authorized by the copyright holders of\nthat material) supplement the terms of this License with terms:\n\n a) Disclaiming warranty or limiting liability differently from the\n terms of sections 15 and 16 of this License; or\n\n b) Requiring preservation of specified reasonable legal notices or\n author attributions in that material or in the Appropriate Legal\n Notices displayed by works containing it; or\n\n c) Prohibiting misrepresentation of the origin of that material, or\n requiring that modified versions of such material be marked in\n reasonable ways as different from the original version; or\n\n d) Limiting the use for publicity purposes of names of licensors or\n authors of the material; or\n\n e) Declining to grant rights under trademark law for use of some\n trade names, trademarks, or service marks; or\n\n f) Requiring indemnification of licensors and authors of that\n material by anyone who conveys the material (or modified versions of\n it) with contractual assumptions of liability to the recipient, for\n any liability that these contractual assumptions directly impose on\n those licensors and authors.\n\n All other non-permissive additional terms are considered \"further\nrestrictions\" within the meaning of section 10. If the Program as you\nreceived it, or any part of it, contains a notice stating that it is\ngoverned by this License along with a term that is a further\nrestriction, you may remove that term. If a license document contains\na further restriction but permits relicensing or conveying under this\nLicense, you may add to a covered work material governed by the terms\nof that license document, provided that the further restriction does\nnot survive such relicensing or conveying.\n\n If you add terms to a covered work in accord with this section, you\nmust place, in the relevant source files, a statement of the\nadditional terms that apply to those files, or a notice indicating\nwhere to find the applicable terms.\n\n Additional terms, permissive or non-permissive, may be stated in the\nform of a separately written license, or stated as exceptions;\nthe above requirements apply either way.\n\n 8. Termination.\n\n You may not propagate or modify a covered work except as expressly\nprovided under this License. Any attempt otherwise to propagate or\nmodify it is void, and will automatically terminate your rights under\nthis License (including any patent licenses granted under the third\nparagraph of section 11).\n\n However, if you cease all violation of this License, then your\nlicense from a particular copyright holder is reinstated (a)\nprovisionally, unless and until the copyright holder explicitly and\nfinally terminates your license, and (b) permanently, if the copyright\nholder fails to notify you of the violation by some reasonable means\nprior to 60 days after the cessation.\n\n Moreover, your license from a particular copyright holder is\nreinstated permanently if the copyright holder notifies you of the\nviolation by some reasonable means, this is the first time you have\nreceived notice of violation of this License (for any work) from that\ncopyright holder, and you cure the violation prior to 30 days after\nyour receipt of the notice.\n\n Termination of your rights under this section does not terminate the\nlicenses of parties who have received copies or rights from you under\nthis License. If your rights have been terminated and not permanently\nreinstated, you do not qualify to receive new licenses for the same\nmaterial under section 10.\n\n 9. Acceptance Not Required for Having Copies.\n\n You are not required to accept this License in order to receive or\nrun a copy of the Program. Ancillary propagation of a covered work\noccurring solely as a consequence of using peer-to-peer transmission\nto receive a copy likewise does not require acceptance. However,\nnothing other than this License grants you permission to propagate or\nmodify any covered work. These actions infringe copyright if you do\nnot accept this License. Therefore, by modifying or propagating a\ncovered work, you indicate your acceptance of this License to do so.\n\n 10. Automatic Licensing of Downstream Recipients.\n\n Each time you convey a covered work, the recipient automatically\nreceives a license from the original licensors, to run, modify and\npropagate that work, subject to this License. You are not responsible\nfor enforcing compliance by third parties with this License.\n\n An \"entity transaction\" is a transaction transferring control of an\norganization, or substantially all assets of one, or subdividing an\norganization, or merging organizations. If propagation of a covered\nwork results from an entity transaction, each party to that\ntransaction who receives a copy of the work also receives whatever\nlicenses to the work the party's predecessor in interest had or could\ngive under the previous paragraph, plus a right to possession of the\nCorresponding Source of the work from the predecessor in interest, if\nthe predecessor has it or can get it with reasonable efforts.\n\n You may not impose any further restrictions on the exercise of the\nrights granted or affirmed under this License. For example, you may\nnot impose a license fee, royalty, or other charge for exercise of\nrights granted under this License, and you may not initiate litigation\n(including a cross-claim or counterclaim in a lawsuit) alleging that\nany patent claim is infringed by making, using, selling, offering for\nsale, or importing the Program or any portion of it.\n\n 11. Patents.\n\n A \"contributor\" is a copyright holder who authorizes use under this\nLicense of the Program or a work on which the Program is based. The\nwork thus licensed is called the contributor's \"contributor version\".\n\n A contributor's \"essential patent claims\" are all patent claims\nowned or controlled by the contributor, whether already acquired or\nhereafter acquired, that would be infringed by some manner, permitted\nby this License, of making, using, or selling its contributor version,\nbut do not include claims that would be infringed only as a\nconsequence of further modification of the contributor version. For\npurposes of this definition, \"control\" includes the right to grant\npatent sublicenses in a manner consistent with the requirements of\nthis License.\n\n Each contributor grants you a non-exclusive, worldwide, royalty-free\npatent license under the contributor's essential patent claims, to\nmake, use, sell, offer for sale, import and otherwise run, modify and\npropagate the contents of its contributor version.\n\n In the following three paragraphs, a \"patent license\" is any express\nagreement or commitment, however denominated, not to enforce a patent\n(such as an express permission to practice a patent or covenant not to\nsue for patent infringement). To \"grant\" such a patent license to a\nparty means to make such an agreement or commitment not to enforce a\npatent against the party.\n\n If you convey a covered work, knowingly relying on a patent license,\nand the Corresponding Source of the work is not available for anyone\nto copy, free of charge and under the terms of this License, through a\npublicly available network server or other readily accessible means,\nthen you must either (1) cause the Corresponding Source to be so\navailable, or (2) arrange to deprive yourself of the benefit of the\npatent license for this particular work, or (3) arrange, in a manner\nconsistent with the requirements of this License, to extend the patent\nlicense to downstream recipients. \"Knowingly relying\" means you have\nactual knowledge that, but for the patent license, your conveying the\ncovered work in a country, or your recipient's use of the covered work\nin a country, would infringe one or more identifiable patents in that\ncountry that you have reason to believe are valid.\n\n If, pursuant to or in connection with a single transaction or\narrangement, you convey, or propagate by procuring conveyance of, a\ncovered work, and grant a patent license to some of the parties\nreceiving the covered work authorizing them to use, propagate, modify\nor convey a specific copy of the covered work, then the patent license\nyou grant is automatically extended to all recipients of the covered\nwork and works based on it.\n\n A patent license is \"discriminatory\" if it does not include within\nthe scope of its coverage, prohibits the exercise of, or is\nconditioned on the non-exercise of one or more of the rights that are\nspecifically granted under this License. You may not convey a covered\nwork if you are a party to an arrangement with a third party that is\nin the business of distributing software, under which you make payment\nto the third party based on the extent of your activity of conveying\nthe work, and under which the third party grants, to any of the\nparties who would receive the covered work from you, a discriminatory\npatent license (a) in connection with copies of the covered work\nconveyed by you (or copies made from those copies), or (b) primarily\nfor and in connection with specific products or compilations that\ncontain the covered work, unless you entered into that arrangement,\nor that patent license was granted, prior to 28 March 2007.\n\n Nothing in this License shall be construed as excluding or limiting\nany implied license or other defenses to infringement that may\notherwise be available to you under applicable patent law.\n\n 12. No Surrender of Others' Freedom.\n\n If conditions are imposed on you (whether by court order, agreement or\notherwise) that contradict the conditions of this License, they do not\nexcuse you from the conditions of this License. If you cannot convey a\ncovered work so as to satisfy simultaneously your obligations under this\nLicense and any other pertinent obligations, then as a consequence you may\nnot convey it at all. For example, if you agree to terms that obligate you\nto collect a royalty for further conveying from those to whom you convey\nthe Program, the only way you could satisfy both those terms and this\nLicense would be to refrain entirely from conveying the Program.\n\n 13. Remote Network Interaction; Use with the GNU General Public License.\n\n Notwithstanding any other provision of this License, if you modify the\nProgram, your modified version must prominently offer all users\ninteracting with it remotely through a computer network (if your version\nsupports such interaction) an opportunity to receive the Corresponding\nSource of your version by providing access to the Corresponding Source\nfrom a network server at no charge, through some standard or customary\nmeans of facilitating copying of software. This Corresponding Source\nshall include the Corresponding Source for any work covered by version 3\nof the GNU General Public License that is incorporated pursuant to the\nfollowing paragraph.\n\n Notwithstanding any other provision of this License, you have\npermission to link or combine any covered work with a work licensed\nunder version 3 of the GNU General Public License into a single\ncombined work, and to convey the resulting work. The terms of this\nLicense will continue to apply to the part which is the covered work,\nbut the work with which it is combined will remain governed by version\n3 of the GNU General Public License.\n\n 14. Revised Versions of this License.\n\n The Free Software Foundation may publish revised and/or new versions of\nthe GNU Affero General Public License from time to time. Such new versions\nwill be similar in spirit to the present version, but may differ in detail to\naddress new problems or concerns.\n\n Each version is given a distinguishing version number. If the\nProgram specifies that a certain numbered version of the GNU Affero General\nPublic License \"or any later version\" applies to it, you have the\noption of following the terms and conditions either of that numbered\nversion or of any later version published by the Free Software\nFoundation. If the Program does not specify a version number of the\nGNU Affero General Public License, you may choose any version ever published\nby the Free Software Foundation.\n\n If the Program specifies that a proxy can decide which future\nversions of the GNU Affero General Public License can be used, that proxy's\npublic statement of acceptance of a version permanently authorizes you\nto choose that version for the Program.\n\n Later license versions may give you additional or different\npermissions. However, no additional obligations are imposed on any\nauthor or copyright holder as a result of your choosing to follow a\nlater version.\n\n 15. Disclaimer of Warranty.\n\n THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY\nAPPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT\nHOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM \"AS IS\" WITHOUT WARRANTY\nOF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,\nTHE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR\nPURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM\nIS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF\nALL NECESSARY SERVICING, REPAIR OR CORRECTION.\n\n 16. Limitation of Liability.\n\n IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING\nWILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS\nTHE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY\nGENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE\nUSE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF\nDATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD\nPARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),\nEVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF\nSUCH DAMAGES.\n\n 17. Interpretation of Sections 15 and 16.\n\n If the disclaimer of warranty and limitation of liability provided\nabove cannot be given local legal effect according to their terms,\nreviewing courts shall apply local law that most closely approximates\nan absolute waiver of all civil liability in connection with the\nProgram, unless a warranty or assumption of liability accompanies a\ncopy of the Program in return for a fee.\n\n END OF TERMS AND CONDITIONS\n\n How to Apply These Terms to Your New Programs\n\n If you develop a new program, and you want it to be of the greatest\npossible use to the public, the best way to achieve this is to make it\nfree software which everyone can redistribute and change under these terms.\n\n To do so, attach the following notices to the program. It is safest\nto attach them to the start of each source file to most effectively\nstate the exclusion of warranty; and each file should have at least\nthe \"copyright\" line and a pointer to where the full notice is found.\n\n \n Copyright (C) \n\n This program is free software: you can redistribute it and/or modify\n it under the terms of the GNU Affero General Public License as published\n by the Free Software Foundation, either version 3 of the License, or\n (at your option) any later version.\n\n This program is distributed in the hope that it will be useful,\n but WITHOUT ANY WARRANTY; without even the implied warranty of\n MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the\n GNU Affero General Public License for more details.\n\n You should have received a copy of the GNU Affero General Public License\n along with this program. If not, see .\n\nAlso add information on how to contact you by electronic and paper mail.\n\n If your software can interact with users remotely through a computer\nnetwork, you should also make sure that it provides a way for users to\nget its source. For example, if your program is a web application, its\ninterface could display a \"Source\" link that leads users to an archive\nof the code. There are many ways you could offer source, and different\nsolutions will be better for different programs; see section 13 for the\nspecific requirements.\n\n You should also get your employer (if you work as a programmer) or school,\nif any, to sign a \"copyright disclaimer\" for the program, if necessary.\nFor more information on this, and how to apply and follow the GNU AGPL, see\n.\n" }, { "path": "README.md", "content": "\n\n
\n\n\"daily.dev\n\n
\n\n# Welcome to the daily.dev repository\n\nWe know how hard it is to be a developer. It doesn't have to be.
\ndaily.dev is the homepage every developer deserves.
\nPersonalized news feed, dev communities, and search, much better than what’s out there. Maybe ;)\n\n[Product Docs][product-docs-link] · [Changelog][changelog-link] · [Report a Bug][report-bug-link] · [Request a Feature][github-discussions-link] · [Swag Store][swag-store-link] · [Brand Assets][brand-book-link]\n\n\n\n[![][chrome-users-shield]][chrome-users-link]\n[![][extension-rating-shield]][extension-rating-link]\n[![][latest-version-shield]][latest-version-link]
\n[![][github-stars-shield]][github-stars-link]\n[![][github-license-shield]][github-license-link]
\n\n**Help more developers suffer less by sharing daily.dev**\n\n[![][share-x-shield]][share-x-link]\n[![][share-telegram-shield]][share-telegram-link]\n[![][share-whatsapp-shield]][share-whatsapp-link]\n[![][share-reddit-shield]][share-reddit-link]\n[![][share-mastodon-shield]][share-mastodon-link]\n[![][share-linkedin-shield]][share-linkedin-link]\n\nWant to contribute? [Run our app locally](https://github.com/dailydotdev/daily?tab=readme-ov-file#-running-dailydev-locally)\n\n\"daily.dev\n
\n👀 Watch it in action → \n\n
\n\n## 💜 About daily.dev\n\n> [!IMPORTANT]\n> Star us to show your support and love for daily.dev ⭐️\n\ndaily.dev is a professional network for developers to learn, collaborate, and grow together. With daily.dev, you can discover a wide variety of professional knowledge, create groups where you can collaborate with other developers you appreciate, and discuss the latest trends in the developer ecosystem. It works offline and is available both as a browser extension and as a Progressive Web App (PWA). \n\n\"daily.dev\n\n
\n Star History\n \n \n \n \n
\n\n## 📌 Get daily.dev\n\ndaily.dev is currently available for Google Chrome and Microsoft Edge. There's also a PWA for mobile devices. \n\nGet it now on:\n\n

\n \n \"Download\n \n \n \"Download\n \n \n \"Download\n \n

\n\n## 📯 Philosophy\n\nWe recognize that developers today have the greatest power as a professional group to drive change and affect the lives of billions. Many platforms provide developers with tools that serve their success or the goals of their workplace, but daily.dev is by design for developers themselves. \n\nWe, as developers, know how challenging it is to grow professionally with so much going on, and that's why we built daily.dev — to make it easy for us to navigate the abundant content and discover all the knowledge they need with zero effort.\n\nYou can use daily.dev to:\n\n\n* 👨‍💻 Learn and stay up-to-date\n\n* 🙌 Interact based on the latest trends in our ecosystem\n\n* 🚀 Collaborate with other developers you know and appreciate\n\n\n## 🌲 daily.dev projects\n\ndaily.dev might look simple on the surface, but actually, it is powered by a complex and robust system of different applications. It contains several services, some are big, others are micro and easy to maintain. Below is the list of different projects that we maintain under daily.dev.\n\n### 🙌 Community & Docs\n\n\n* [daily](https://github.com/dailydotdev/daily) - This is the repository you are currently at. It serves as a central place for all the projects. It contains documentation, community ideas, suggestions, and whatnot.\n\n* [docs](https://github.com/dailydotdev/docs) - This is the repository for official product documentation of daily.dev.\n\n\n### 🎨 Frontend\n\n\n* [apps](https://github.com/dailydotdev/apps) - Monorepo with all the frontend-related projects since daily.dev 3.0. This includes both the extension and the webapp.\n\n\n### 🎈 Others\n\n\n* [action-devcard](https://github.com/dailydotdev/action-devcard) - GitHub Actions for adding daily DevCard to GitHub profile. Read [the guide](https://daily.dev/blog/adding-the-daily-devcard-to-your-github-profile) to set it up.\n\n\n## 🚀 Running daily.dev locally\n\n> [!NOTE]\n> Currently, not all services are ready (or needed) for local environments, so Daily Redirector, Daily Monetization, and Authentication services are not available for you.\n\n\nTo spin up a local environment, you will need Docker. Do the steps below and you should be able to start trying to center a div:\n- Fork this repo: https://github.com/dailydotdev/apps\n- Pull it locally\n- Run `docker compose up`\n- Apply all migrations by running `docker compose exec daily-api node ./node_modules/typeorm/cli.js migration:run -d src/data-source.js`\n- Once done, seed your local data by running `docker compose exec daily-api node ./bin/import`\n- Then lastly, run `npm run dev:oss`\n- The app should run at `http://localhost:5002/`\n\n## 🙌 Want to contribute?\n\nWe are open to all kinds of contributions. If you want to:\n\n\n* 🤔 Suggest a feature\n\n* 🐛 Report an issue\n\n* 📖 Improve documentation\n\n* 👨‍💻 Contribute to the code\n\n\nYou are more than welcome. Before contributing, kindly check our [guidelines](https://github.com/dailydotdev/.github/blob/master/CONTRIBUTING.md).\n\n## 💬 What do you think of daily.dev?\n\n
\n

\"Twitter  Tweet us @dailydotdev to share your thoughts and stay up-to-date.

\n

\"daily.dev  Check out our Product Hunt page.

\n

\"daily.dev  Visit our home for a bunch of useful links.

\n

\"daily.dev  See our Chrome Store page to grab the extension or share your feedback.

\n

\"daily.dev  Check us out on Microsoft Edge Addons and let us know your thoughts.

\n\n## 📑 License\nLicensed under [AGPL-3.0](https://github.com/dailydotdev/daily/blob/master/LICENSE).\n\n
\n\n[![][back-to-top]](#readme-top)\n\n
\n\n\n\n[back-to-top]: https://img.shields.io/badge/-BACK_TO_TOP-151515?style=flat-square\n[product-docs-link]: https://docs.daily.dev/docs/intro\n[changelog-link]: https://app.daily.dev/sources/daily_updates\n[report-bug-link]: https://github.com/dailydotdev/daily/issues/new?assignees=&labels=Type%3A+Bug&projects=&template=---bug-report.yml&title=%F0%9F%90%9B+BUG%3A+\n[github-discussions-link]: https://github.com/dailydotdev/daily/discussions/new?category=feature-requests\n[swag-store-link]: https://store.daily.dev/\n[brand-book-link]: https://brand.daily.dev/\n\n\n\n[chrome-users-shield]: https://img.shields.io/chrome-web-store/users/jlmpjdjjbgclbocgajdjefcidcncaied?style=flat-square&logo=googlechrome&logoColor=white&label=chrome%20active%20users&labelColor=black&color=9E15D9\n[chrome-users-link]: https://chromewebstore.google.com/detail/dailydev-the-homepage-dev/jlmpjdjjbgclbocgajdjefcidcncaied\n[extension-rating-shield]: https://img.shields.io/amo/rating/daily?style=flat-square&labelColor=black&color=0FC54F\n[extension-rating-link]: https://api.daily.dev/get\n[latest-version-shield]: https://img.shields.io/chrome-web-store/v/jlmpjdjjbgclbocgajdjefcidcncaied?style=flat-square&label=latest%20version&labelColor=black&color=0FC54F\n[latest-version-link]: https://api.daily.dev/get\n[github-stars-shield]: https://img.shields.io/github/stars/dailydotdev/daily?style=flat-square&logo=github&labelColor=black&color=508CF9\n[github-stars-link]: https://github.com/dailydotdev/daily/stargazers\n[github-license-shield]: https://img.shields.io/github/license/dailydotdev/daily?style=flat-square&logo=github&labelColor=black&color=508CF9\n[github-license-link]: https://github.com/dailydotdev/daily/issues\n\n\n\n[share-linkedin-link]: https://www.linkedin.com/shareArticle?mini=true&url=https%3A//daily.dev\n[share-linkedin-shield]: https://img.shields.io/badge/-share%20on%20linkedin-black?labelColor=black&logo=linkedin&logoColor=white&style=flat-square\n[share-mastodon-link]: https://mastodon.social/share?text=I%20recently%20started%20using%20daily.dev%20-%20It's%20like%20a%20newsfeed%20but%20just%20for%20dev%20content.%20Pretty%20handy%20for%20staying%20up%20to%20date%20without%20the%20usual%20internet%20rabbit%20hole.%20Might%20be%20a%20nice%20break%20from%20the%20usual%20sites.&url=\n[share-mastodon-shield]: https://img.shields.io/badge/-share%20on%20mastodon-black?labelColor=black&logo=mastodon&logoColor=white&style=flat-square\n[share-reddit-link]: http://www.reddit.com/submit?url=https%3A%2F%2Fdaily.dev&title=I%20recently%20started%20using%20daily.dev%20-%20It's%20like%20a%20newsfeed%20but%20just%20for%20dev%20content.%20Pretty%20handy%20for%20staying%20up%20to%20date%20without%20the%20usual%20internet%20rabbit%20hole.%20Might%20be%20a%20nice%20break%20from%20the%20usual%20sites.\n[share-reddit-shield]: https://img.shields.io/badge/-share%20on%20reddit-black?labelColor=black&logo=reddit&logoColor=white&style=flat-square\n[share-telegram-link]: https://t.me/share/url?url=https%3A//daily.dev&text=I%20recently%20started%20using%20daily.dev%20-%20It's%20like%20a%20newsfeed%20but%20just%20for%20dev%20content.%20Pretty%20handy%20for%20staying%20up%20to%20date%20without%20the%20usual%20internet%20rabbit%20hole.%20Might%20be%20a%20nice%20break%20from%20the%20usual%20sites.\n[share-telegram-shield]: https://img.shields.io/badge/-share%20on%20telegram-black?labelColor=black&logo=telegram&logoColor=white&style=flat-square\n[share-whatsapp-link]: https://api.whatsapp.com/send?text=I%20recently%20started%20using%20daily.dev%20-%20It's%20like%20a%20newsfeed%20but%20just%20for%20dev%20content.%20Pretty%20handy%20for%20staying%20up%20to%20date%20without%20the%20usual%20internet%20rabbit%20hole.%20Might%20be%20a%20nice%20break%20from%20the%20usual%20sites.%20https%3A%2F%2Fdaily.dev\n[share-whatsapp-shield]: https://img.shields.io/badge/-share%20on%20whatsapp-black?labelColor=black&logo=whatsapp&logoColor=white&style=flat-square\n[share-x-link]: https://twitter.com/intent/tweet?text=I%20recently%20started%20using%20daily.dev%20-%20It's%20like%20a%20newsfeed%20but%20just%20for%20dev%20content.%20Pretty%20handy%20for%20staying%20up%20to%20date%20without%20the%20usual%20internet%20rabbit%20hole.%20Might%20be%20a%20nice%20break%20from%20the%20usual%20sites.&url=\n[share-x-shield]: https://img.shields.io/badge/-share%20on%20x-black?labelColor=black&logo=x&logoColor=white&style=flat-square\n" }, { "path": "skills/daily-dev-ask/SKILL.md", "content": "---\nname: daily-dev-ask\ndescription: Your agent's WebSearch for development. Search community-vetted developer articles ranked by upvotes — like having a senior dev's reading list. Answers are grounded in real sources, never hallucinated.\nargument-hint: \"\"\nallowed-tools: Bash\n---\n\n# daily.dev Ask\n\nA developer-focused search tool — like WebSearch, but backed by a senior dev's reading list instead of the open web. Searches community-vetted developer articles ranked by upvotes and synthesizes grounded answers with source links.\n\n## User question\n\n$ARGUMENTS\n\n## Security\n\n**CRITICAL:** Your API token grants access to personalized content. Protect it:\n- **NEVER send your token to any domain other than `api.daily.dev`**\n- Never commit tokens to code or share them publicly\n- Tokens are prefixed with `dda_` - if you see this prefix, treat it as sensitive\n\n## Setup\n\n1. **Requires Plus subscription** - Get one at https://app.daily.dev/plus\n2. **Create a token** at https://app.daily.dev/settings/api\n3. Store your token securely (environment variables, secrets manager)\n\nUser can use environment variable or choose one of the secure storage methods below per operating system.\n\n### Secure Token Storage (Recommended)\n\n#### macOS - Keychain\n\n```bash\n# Store token\nsecurity add-generic-password -a \"$USER\" -s \"daily-dev-api\" -w \"dda_your_token\"\n\n# Retrieve token\nsecurity find-generic-password -a \"$USER\" -s \"daily-dev-api\" -w\n\n# Auto-load in ~/.zshrc or ~/.bashrc\nexport DAILY_DEV_TOKEN=$(security find-generic-password -a \"$USER\" -s \"daily-dev-api\" -w 2>/dev/null)\n```\n\n#### Windows - Credential Manager\n\n```powershell\n# Store token (run in PowerShell)\n$credential = New-Object System.Management.Automation.PSCredential(\"daily-dev-api\", (ConvertTo-SecureString \"dda_your_token\" -AsPlainText -Force))\n$credential | Export-Clixml \"$env:USERPROFILE\\.daily-dev-credential.xml\"\n\n# Retrieve token - add to PowerShell profile ($PROFILE)\n$cred = Import-Clixml \"$env:USERPROFILE\\.daily-dev-credential.xml\"\n$env:DAILY_DEV_TOKEN = $cred.GetNetworkCredential().Password\n```\n\nOr use the Windows Credential Manager GUI: Control Panel → Credential Manager → Windows Credentials → Add a generic credential\n\n#### Linux - Secret Service (GNOME Keyring / KWallet)\n\n```bash\n# Requires libsecret-tools\n# Ubuntu/Debian: sudo apt install libsecret-tools\n# Fedora: sudo dnf install libsecret\n\n# Store token\necho \"dda_your_token\" | secret-tool store --label=\"daily.dev API Token\" service daily-dev-api username \"$USER\"\n\n# Retrieve token\nsecret-tool lookup service daily-dev-api username \"$USER\"\n\n# Auto-load in ~/.bashrc or ~/.zshrc\nexport DAILY_DEV_TOKEN=$(secret-tool lookup service daily-dev-api username \"$USER\" 2>/dev/null)\n```\n\n## Workflow\n\n### 1. Determine the API token\n\nCheck if `DAILY_DEV_TOKEN` environment variable is available. If not set, try to retrieve it from the OS secure storage before asking the user for help:\n\n**macOS:**\n```bash\nexport DAILY_DEV_TOKEN=$(security find-generic-password -a \"$USER\" -s \"daily-dev-api\" -w 2>/dev/null)\n```\n\n**Linux:**\n```bash\nexport DAILY_DEV_TOKEN=$(secret-tool lookup service daily-dev-api username \"$USER\" 2>/dev/null)\n```\n\n**Windows (PowerShell):**\n```powershell\n$cred = Import-Clixml \"$env:USERPROFILE\\.daily-dev-credential.xml\" 2>$null; $env:DAILY_DEV_TOKEN = $cred.GetNetworkCredential().Password\n```\n\nIf the token is still empty after trying secure storage, direct the user to the Setup section above.\n\n### 2. Search iteratively — treat daily.dev like a search engine\n\nUse the two endpoints below as many times as needed to explore the user's question. There is no hard limit on the number of queries — search like you would with web search.\n\n**Keyword search endpoint:**\n```bash\ncurl -s -H \"Authorization: Bearer $DAILY_DEV_TOKEN\" \"https://api.daily.dev/public/v1/recommend/keyword?q={keywords}&limit=20\"\n```\n\n**Semantic search endpoint:**\n```bash\ncurl -s -H \"Authorization: Bearer $DAILY_DEV_TOKEN\" \"https://api.daily.dev/public/v1/recommend/semantic?q={query}&limit=20\"\n```\n\nBoth return:\n```json\n{\n \"data\": [\n {\n \"id\": \"...\",\n \"title\": \"Article title\",\n \"url\": \"https://...\",\n \"summary\": \"Article summary...\",\n \"tags\": [\"tag1\", \"tag2\"],\n \"readTime\": 7,\n \"numUpvotes\": 342,\n \"numComments\": 28,\n \"source\": { \"name\": \"Publisher Name\" }\n }\n ]\n}\n```\n\n#### Search strategy\n\n1. **Initial searches** — Start with a keyword search (core technical terms) and a semantic search (full question). You can run these in parallel.\n\n2. **Analyze and identify gaps** — Review the results:\n - Did I find enough to fully answer the question?\n - Are there sub-topics or related concepts I haven't explored?\n - Did article titles/tags hint at related terms worth searching?\n\n3. **Follow-up searches** — For any gaps or interesting leads:\n - Search for specific tools, libraries, or frameworks mentioned in results\n - Try synonyms or alternative terminology\n - Search for sub-topics the user might care about\n\n4. **Stop when done** — Stop searching when:\n - You have enough articles to give a good answer, OR\n - Follow-up searches return no new results\n\n### 3. Deduplicate results\n\nMerge results from all search rounds, removing duplicates by `id`. Keep all unique articles.\n\n### 4. Synthesize the answer\n\nUsing all collected articles, compose a response:\n\n---\n\n**Answer the question directly**, grounding your response in the article content. Reference specific articles when making claims. Use the `summary`, `title`, and `tags` to understand each article's angle.\n\n**Use engagement signals to weight credibility:**\n- Higher `numUpvotes` = more community validation\n- Higher `numComments` = more discussion/nuance available\n- `readTime` helps gauge depth\n\n**Sources section** — list the most relevant articles:\n\n```\n### Sources from daily.dev\n\n1. [Article Title](url) — summary snippet (⬆️ upvotes · 💬 comments)\n2. [Article Title](url) — summary snippet (⬆️ upvotes · 💬 comments)\n...\n```\n\n---\n\n### 5. Handle edge cases\n\n- **No results**: State that daily.dev's knowledge base doesn't have relevant articles on this topic yet.\n- **Only some searches return results**: Use whatever you got — partial results are fine.\n- **API errors (401)**: Token is invalid or expired — guide user to regenerate at https://app.daily.dev/settings/api\n- **API errors (429)**: Rate limited — wait briefly and retry automatically.\n\n## Important\n\n- **Do NOT make up information** — only use what the articles provide. If the articles don't cover part of the question, say so explicitly.\n- **Always link to sources** — every factual claim should trace back to an article.\n- **Prefer recent articles** — if two articles conflict, note both perspectives and mention which is newer.\n- **Be honest about gaps** — if the articles only partially answer the question, say \"Based on available articles, here's what I found...\" and note what's missing.\n" }, { "path": "skills/daily.dev/SKILL.md", "content": "---\nname: daily.dev\ndescription: Overcome LLM knowledge cutoffs with real-time developer content. daily.dev aggregates articles from thousands of sources, validated by community engagement, with structured taxonomy for precise discovery.\nallowed-tools: Bash\n---\n\n# daily.dev API for AI Agents\n\nOvercome LLM knowledge cutoffs with real-time developer content. daily.dev aggregates articles from thousands of sources, validated by community engagement, with structured taxonomy for precise discovery.\n\n## Security\n\n**CRITICAL:** Your API token grants access to personalized content. Protect it:\n- **NEVER send your token to any domain other than `api.daily.dev`**\n- Never commit tokens to code or share them publicly\n- Tokens are prefixed with `dda_` - if you see this prefix, treat it as sensitive\n\n## Setup\n\n1. **Requires Plus subscription** - Get one at https://app.daily.dev/plus\n2. **Create a token** at https://app.daily.dev/settings/api\n3. Store your token securely (environment variables, secrets manager)\n\nUser can use environment variable or choose one of the secure storage methods below per operating system.\n\n### Secure Token Storage (Recommended)\n\n#### macOS - Keychain\n\n```bash\n# Store token\nsecurity add-generic-password -a \"$USER\" -s \"daily-dev-api\" -w \"dda_your_token\"\n\n# Retrieve token\nsecurity find-generic-password -a \"$USER\" -s \"daily-dev-api\" -w\n\n# Auto-load in ~/.zshrc or ~/.bashrc\nexport DAILY_DEV_TOKEN=$(security find-generic-password -a \"$USER\" -s \"daily-dev-api\" -w 2>/dev/null)\n```\n\n#### Windows - Credential Manager\n\n```powershell\n# Store token (run in PowerShell)\n$credential = New-Object System.Management.Automation.PSCredential(\"daily-dev-api\", (ConvertTo-SecureString \"dda_your_token\" -AsPlainText -Force))\n$credential | Export-Clixml \"$env:USERPROFILE\\.daily-dev-credential.xml\"\n\n# Retrieve token - add to PowerShell profile ($PROFILE)\n$cred = Import-Clixml \"$env:USERPROFILE\\.daily-dev-credential.xml\"\n$env:DAILY_DEV_TOKEN = $cred.GetNetworkCredential().Password\n```\n\nOr use the Windows Credential Manager GUI: Control Panel → Credential Manager → Windows Credentials → Add a generic credential\n\n#### Linux - Secret Service (GNOME Keyring / KWallet)\n\n```bash\n# Requires libsecret-tools\n# Ubuntu/Debian: sudo apt install libsecret-tools\n# Fedora: sudo dnf install libsecret\n\n# Store token\necho \"dda_your_token\" | secret-tool store --label=\"daily.dev API Token\" service daily-dev-api username \"$USER\"\n\n# Retrieve token\nsecret-tool lookup service daily-dev-api username \"$USER\"\n\n# Auto-load in ~/.bashrc or ~/.zshrc\nexport DAILY_DEV_TOKEN=$(secret-tool lookup service daily-dev-api username \"$USER\" 2>/dev/null)\n```\n\n## Resolving the API token\n\nCheck if `DAILY_DEV_TOKEN` environment variable is available. If not set, try to retrieve it from the OS secure storage before asking the user for help:\n\n**macOS:**\n```bash\nexport DAILY_DEV_TOKEN=$(security find-generic-password -a \"$USER\" -s \"daily-dev-api\" -w 2>/dev/null)\n```\n\n**Linux:**\n```bash\nexport DAILY_DEV_TOKEN=$(secret-tool lookup service daily-dev-api username \"$USER\" 2>/dev/null)\n```\n\n**Windows (PowerShell):**\n```powershell\n$cred = Import-Clixml \"$env:USERPROFILE\\.daily-dev-credential.xml\" 2>$null; $env:DAILY_DEV_TOKEN = $cred.GetNetworkCredential().Password\n```\n\nIf the token is still empty after trying secure storage, direct the user to the Setup section above.\n\n## Authentication\n\n```\nAuthorization: Bearer $DAILY_DEV_TOKEN\n```\n\n## Base URL\n\n```\nhttps://api.daily.dev/public/v1\n```\n\n## API Reference\n\nFull OpenAPI spec: https://api.daily.dev/public/v1/docs/json\n\nTo fetch details for a specific endpoint (e.g. response schema):\n```bash\ncurl -s https://api.daily.dev/public/v1/docs/json | jq '.paths[\"/feeds/foryou\"].get'\n```\n\nTo fetch a component schema (replace `def-17` with schema name from $ref):\n```bash\ncurl -s https://api.daily.dev/public/v1/docs/json | jq '.components.schemas[\"def-17\"]'\n```\n\n### Available Endpoints\n!`curl -s https://api.daily.dev/public/v1/docs/json | jq -r '.paths | to_entries | map(.key as $path | .value | to_entries | map(.key as $method | {tag: (.value.tags[0] // \"other\"), line: (\"\\(.key | ascii_upcase) \\($path)\" + (if .value.description then \" - \\(.value.description)\" else \"\" end) + (if (.value.parameters | length) > 0 then \"\\n Params: \" + ([.value.parameters[] | \"\\(.name)(\\(.in)): \\(.description // .schema.type)\"] | join(\"; \")) else \"\" end) + (if .value.requestBody then \"\\n Body: \" + (.value.requestBody.content[\"application/json\"].schema | if .properties then ([.properties | to_entries[] | \"\\(.key)\"] | join(\", \")) elif .\"$ref\" then (.\"$ref\" | split(\"/\") | last) else \"object\" end) else \"\" end))})) | flatten | group_by(.tag) | map(\"#### \\(.[0].tag)\\n\" + (map(.line) | join(\"\\n\\n\"))) | join(\"\\n\\n\")'`\n\n## Agent Use Cases\n\n**Why daily.dev for agents?** LLMs have knowledge cutoffs. daily.dev provides real-time, community-validated developer content with structured taxonomy across thousands of sources. Agents can use this to stay current, get diverse perspectives, and understand what the developer community actually cares about.\n\nThese examples show how AI agents can combine daily.dev APIs with external context to create powerful developer workflows.\n\n### 🔍 GitHub Repo → Personalized Feed\nScan a user's GitHub repositories to detect their actual tech stack from `package.json`, `go.mod`, `Cargo.toml`, `requirements.txt`, etc. Then:\n- Fetch `/tags` to see all available tags for deterministic matching\n- Auto-follow matching tags via `/feeds/filters/tags/follow`\n- Create a custom feed tuned to their stack with `/feeds/custom/`\n- Surface trending articles about their specific dependencies\n\n**Trigger:** \"Set up daily.dev based on my GitHub projects\"\n\n### 🛠️ GitHub → Auto-fill Stack Profile\nAnalyze a user's GitHub activity to build their daily.dev tech stack profile automatically:\n- Scan repositories for languages, frameworks, and tools actually used in code\n- Search `/profile/stack/search` to find matching technologies on daily.dev\n- Populate their stack via `POST /profile/stack/` organized by section (languages, frameworks, tools)\n- Update `/profile/` bio based on their primary technologies and contributions\n\n**Trigger:** \"Build my daily.dev profile from my GitHub\"\n\n### 🚀 New Project → Curated Onboarding\nWhen a user initializes a new project or clones a repo:\n- Analyze the tech choices from config files\n- Create a dedicated custom feed filtered to exactly those technologies\n- Build a \"Getting Started\" bookmark list with foundational articles\n- Block irrelevant tags to keep the feed focused on the project scope\n\n**Trigger:** \"Help me learn the stack for this project\"\n\n### 📊 Weekly Digest → Synthesized Briefing\nCompile a personalized weekly summary by:\n- Fetching `/feeds/foryou` and `/feeds/popular` filtered by user's followed tags\n- Cross-referencing with their GitHub activity to prioritize relevant topics\n- Summarizing key articles and trending discussions\n- Delivering as a structured briefing with links to full posts\n\n**Trigger:** Scheduled, or \"Give me my weekly dev news\"\n\n### 📚 Research Project Workspace\nWhen a user wants to deep-dive into a topic (e.g., \"I want to learn Kubernetes\"):\n- Create a custom feed via `/feeds/custom/` filtered to that topic\n- Set up a matching bookmark list via `POST /bookmarks/lists` to collect the best finds\n- As the user reads, save articles to the list with `POST /bookmarks/`\n- Track learning progress: compare bookmarked posts vs. new feed items\n- Adjust feed filters over time as understanding deepens (beginner → advanced content)\n\n**Trigger:** \"Start a research project on [topic]\"\n\n### 🧠 Agent Self-Improvement Feed\nAgents can overcome their knowledge cutoff by maintaining their own custom feed:\n- Create a custom feed via `/feeds/custom/` for technologies the agent frequently assists with\n- Periodically fetch `/feeds/custom/{feedId}` to ingest recent articles\n- Use `/posts/{id}` to read full summaries and key points\n- Agent can now provide advice with current information: \"As of this week, the recommended approach is...\"\n- Continuously adapt the feed filters based on what users are asking about\n\n**Trigger:** Agent background process, or \"What's new in [technology] since your training?\"\n\n### 🔀 Multi-Source Synthesis\nGet balanced perspectives by aggregating content across publishers:\n- Search `/search/posts` for a topic to find coverage from multiple sources\n- Use `/search/sources` to identify authoritative publishers on the topic\n- Fetch posts from different sources via `/feeds/source/{source}`\n- Synthesize diverse viewpoints into a balanced summary with citations\n- Surface where sources agree vs. disagree on best practices\n\n**Trigger:** \"What are the different perspectives on [topic]?\" or \"Compare approaches to [problem]\"\n\n### 📈 Trending Radar\nHelp users stay ahead by monitoring community signals:\n- Fetch `/feeds/popular` to detect what's gaining traction right now\n- Cross-reference with user's followed tags to surface relevant trends\n- Use `/feeds/discussed` to find topics sparking active debate\n- Alert users when technologies in their stack are trending (new releases, security issues, paradigm shifts)\n- Use `/tags` to fetch the full tag catalog and `/search/tags` to explore adjacent trending topics\n\n**Trigger:** \"What should I be paying attention to?\" or \"What's trending in [area]?\"\n\n## Rate Limits\n\n* **60 requests per minute** per user\n\nCheck response headers:\n- `X-RateLimit-Limit` - Maximum requests allowed per window\n- `X-RateLimit-Remaining` - Requests remaining in current window\n- `X-RateLimit-Reset` - Unix timestamp when the window resets\n- `Retry-After` - Seconds to wait (only when rate limited)\n\n## Errors\n\n| Code | Meaning |\n|------|---------|\n| 401 | Invalid or missing token |\n| 403 | Plus subscription required |\n| 404 | Resource not found |\n| 429 | Rate limit exceeded |\n\n**Error Response Format:**\n```json\n{\n \"error\": \"error_code\",\n \"message\": \"Human readable message\"\n}\n```\n" } ]