Skip to content

Latest commit

 

History

History
49 lines (41 loc) · 2.64 KB

File metadata and controls

49 lines (41 loc) · 2.64 KB

@AGENTS.md

Project: Hurricane Sandy (2012), ATMO 180 Signature Assignment

What this is

A Next.js website analyzing Hurricane Sandy for the ATMO 180 (Severe Weather & Climate Change) signature assignment at the University of Arizona. The site is framed as a consultant briefing leadership on a past disaster and planning for future events.

Tech stack

  • Next.js 16 (App Router) with TypeScript
  • Tailwind CSS for styling
  • Deployed to Vercel (auto-deploys from main)
  • GitHub repo: fjbarrett/atmo180-hurricane-sandy

Git workflow

  • Always use feature branches: never commit directly to main
  • Branch naming: feat/description, fix/description, content/description
  • Write clear, imperative commit messages: lead with the verb ("Add ...", "Fix ..."). The subject says what changed; a short body says why, only if it isn't obvious. Plain subjects, not conventional-commit prefixes (feat:, fix(scope):), which read as agent-generated.
  • Create pull requests with descriptive summaries for every merge to main
  • This repo should look recruiter-ready: clean history, meaningful PRs

Assignment rubric mapping

The site structure maps directly to the grading rubric (225 points total):

Route Rubric Category (50 pts each)
/regional-climate Interpreting Regional Climate & Relationship to the Hazard
/socioeconomic-impact Assess Socio-economic Conditions & Mitigation Strategies
/climate-change Evaluating Climate Change Impact on the Disaster
(across all pages) Graphical and Quantitative Analysis
/bibliography APA-formatted references + required AI-use summary

Content guidelines

  • Aim for mastery level on all rubric criteria
  • Include graphs and data throughout, not just text
  • Tone: Frank's formal voice; professional and evidence-based, not consultant copywriting
  • All prose (on-page copy, docs, commits, PRs) follows the writing-style overlay in AGENTS.md, which is derived from the Barrett writing framework in ~/Code/barrett-writing (source of truth: writing-framework.md, style-prompt.md). On-page copy uses the formal register: lead with substance, even declaratives (median ~16 words), concrete numbers, contractions where natural, and say each point once. No engineered contrast pairs or punchline closers.
  • All sources must be cited and listed in APA format in the bibliography
  • The assignment explicitly requires NOT being a research paper: keep content visual and structured, not wall-of-text

Components

  • Section: reusable page wrapper with title/subtitle
  • Navigation: responsive nav with mobile menu
  • Footer: site-wide footer