Starter prompt for your coding agent

The hasanat-builder skill gives your coding agent a disciplined path: shape one small first outcome with you, clone the official starter, run it locally, and verify the page before adding sign-in, a database, or deployment.

The prompt works with coding agents that can run commands and read files, such as GitHub Copilot, Claude Code, or Cursor.

Three steps

1. Review the source. Read the skill instructions before giving them to your agent.
2. Copy the prompt exactly as shown and paste it into your coding agent. There is nothing to customize.
3. Answer its first question: it starts by asking what you want to build.

The prompt

Help me start a small working Hasanat project.

Begin by asking me what I want to build. Do not ask me to rewrite or customize this prompt. After I answer, ask at most two short follow-up questions only if needed to identify:

- who the first version is for and what problem it solves;
- the one useful action the first local page should support.

Then summarize the first milestone in one sentence and continue without waiting for me to prepare a formal brief.

First, check whether all five Hasanat skills are available: hasanat-builder, hasanat-auth, hasanat-d1, hasanat-design, and hasanat-deploy. If any are missing:

1. Download the validated complete pack, manifest, and verifier from https://platform.hasanat.dev/skills/ to a temporary directory: hasanat-skills.skill, hasanat-skills.manifest.json, and verify-hasanat-skills.mjs.
2. Run node verify-hasanat-skills.mjs hasanat-skills.skill hasanat-skills.manifest.json. Do not install the pack if verification fails. Then show me its file listing with unzip -l and confirm that it contains one directory for each of the five skills. Briefly explain that skills are instructions and scripts the coding agent will follow.
3. Ask once for approval to install the missing skills. Do not overwrite any existing skill directory.
4. After approval, create .agents/skills in the current project and extract the pack there:

mkdir -p .agents/skills
unzip -n <temporary-path>/hasanat-skills.skill -d .agents/skills

Then load and follow hasanat-builder, loading the companion skills only when you reach authentication, database, design, or deployment work.

Keep the first milestone strict: define one useful first-page outcome, clone the public official Hasanat starter over HTTPS into a new folder, install its locked dependencies, copy .env.example, start the dev server, and verify the page in a browser. Do not require GitHub login, OAuth credentials, D1, deployment, or secrets before I can see something working locally. Continue shaping and implementing the idea with me after that checkpoint.

What happens next

• The agent asks what you want to build, then at most two short follow-up questions if needed.
• It summarizes the first milestone in one sentence.
• It checks for the five skills. If any are missing, it downloads the pack to a temporary folder, verifies it, and asks once for approval before installing. Details are on the skills pack page.
• It clones the starter, installs dependencies, starts the development server, and opens the page in a browser.

First success checkpoint

A real page running at the local URL Astro prints. Sign-in, a database, and deployment are later, optional steps.

If you are working on a project with a spec

Start with the prompt in section 12 of the project’s spec instead, because it points the agent to the brief and the spec first. See from spec to first version (in Arabic).

If your agent cannot download files

Download and verify the pack yourself by following the skills pack page, then paste the prompt.