skills/resources/SKILL.md

---
name: resources
description: Show the participant's resource hub for working through the hackathon with Codex, including docs, inspiration, and anti-pattern guidance. Use when the user wants hackathon resources, wants inspiration, or needs a reminder of what kinds of projects to avoid.
---

# Resources

## Purpose

Update state for Step 3, compose the Resources chat response, and explain the two available paths: continue directly to submission prep or enter the optional guided build tool.

Chat is the primary participant interface. Keep responses text-first so they render in any Codex host; the bundled `devpost` MCP server supplies rich inline visuals on hosts that support them.

## Required Data Source

Official event data comes from the `devpost` MCP server — follow **Devpost MCP Server** in `references/plugin-runtime.md` (call only what you need, never verify or set up the server, degrade in one line on failure).

Draw on these only as needed: `devpost.get_hackathon_overview`, `devpost.get_key_dates`, `devpost.get_announcements`. Use the local `references/` files for evergreen guidance (archetypes, anti-patterns).

## Required References

Read these files before responding:

- `references/plugin-runtime.md`
- `references/content/steps/resources.md`
- `references/config/hackathon.json`
- `references/anti-patterns.md`

## Preconditions

Read `.devpost-hackathon-state.json`.

If the state file does not exist, direct the user to `$start-hackathon`.

If `rules_acknowledged` is not `true`, tell the user to finish `$review-hackathon-rules` first. This is a blocker before the rest of the workflow.

## Response Content

The Resources response should help the participant understand:

- useful in-app resources
- strong project archetypes
- anti-patterns to avoid
- the fork: either enter the guided build tool (`$build-onboard`) or skip it and build the project now with Codex, running `$prepare-submission` only once there is something built to submit
- the optional guided build tool nested inside Step 3

The optional guided build tool is command-driven, not clickable routing in a side pane.

Visible build sequence:

`Ideate -> Scope -> PRD -> Spec -> Checklist -> Build`

Command sequence:

`$build-onboard -> $build-scope -> $build-prd -> $build-spec -> $build-checklist -> $build-project`

Do not render images, posters, or other media in chat.

## Hackathon Resources (live, from the MCP)

Render the hackathon's own resources in chat — a condensed version of the Resources tab on the hackathon's Devpost site. Call the `get_hackathon_overview` MCP tool (bundled `devpost` server, PUBLIC — needs only `hackathon.slug`) and use its `resources_text` / `resources_html` field: pull out the key links and render them as **live markdown hyperlinks**, one short line each (condense — do not dump the whole blob). These chat links are the real resources.

**Only real resources, or none.** If the hackathon returns no resources (or the call fails), show no resource links at all — skip the section without comment beyond one short clause. Never pad the list from other files, web search, or memory: a resource the host didn't publish is not a hackathon resource (see **Never present unofficial data as official** in `references/plugin-runtime.md`).

## Presentation Output

Compose the response in-context per `references/plugin-runtime.md` ("Composing the Response"): read `references/content/steps/resources.md`, strip maintainer `<!-- -->` comments, interpolate the event name, then present a short stage headline, the page content, and the next-step callout. Do not run any script.

## State Update

After showing resources:

- add `resources` to `completed_stages` if needed
- set `current_stage` to `resources`
- set `next_command` to `prepare-submission` (the next tracked stage — but present it as "when your build is ready", never as the immediate next step; the participant builds first, guided or not)
- preserve registration and deadline fields

Do not mark the optional guided build tool active unless the user chooses it or runs `$build-onboard`.

## Chat Output

Keep chat output minimal.

Do not hand-write a separate dashboard. Let the CLI composer render the response.

Respond with:

- note that the guided build tool is optional — always say so, every time it comes up — and that it introduces best practices for coding AI projects, nested inside Step 3
- one or two sentences explaining the fork: guided planning vs. building on your own
- invitation to ask questions about which path fits their project
- do NOT end with a single `$prepare-submission` callout line — that misleads participants into thinking submission prep is the immediate next step before they have built anything. End with the two-path callout instead:

```text
Want the guided path? Say so — or type `$build-onboard`. It'll get you to a proof of concept; making it great stays your job.
Building on your own? Start building with Codex now — when your project feels ready to submit, type `$prepare-submission`.
```

If composer generation fails, use a compact text fallback:

- current stage: Resources
- the two-path callout above (guided `$build-onboard`, or build now and `$prepare-submission` when ready)