agentleFS
f13if13i/f13i-cli/skills/netlify-deploy/SKILL.md

netlify-deploy

Skill0 starsChanged 3 months agoNo licenceView on GitHub

Build, validate, version, and deploy the full f13i.com site to Netlify. ALWAYS use this skill when Farhan says "deploy to Netlify", "push the site", "deploy f13i.com", "update the live site", "Netlify deploy", "push my changes", or any variation of wanting to ship changes to f13i.com. Also trigger automatically when the website-advisor skill has been run and Farhan says "accept these changes" or "implement the improvements". This skill builds the complete deploy folder (index.html, fair-use.html, pricing-problem.html, resources.html, _redirects, og.png), validates all files before touching Netlify, creates a versioned archive, and deploys via Netlify Drop. It never deploys without validation passing and never deploys only index.html — the full folder is always required. Do NOT use for general Netlify questions or other people's sites.

15 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use changelog-generator, test-driven-development and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ArogyaReddySkill

    changelog-generator

    Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

    Also in 3 projects that use this

  • OpenAISkill

    test-driven-development

    Use when implementing any feature or bugfix, before writing implementation code

    Also in 3 projects that use this

  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.