1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
|
# AGENTS.md
## Project
This repository is a personal website built with ASP.NET Core Razor Pages on .NET 10.
The site should stay as close to a static site as practical while still using Razor Pages for structure, layouts, routing, and maintainability.
## Primary Goal
Minimalism is a major goal.
When making changes, prefer:
- fewer files
- fewer dependencies
- less JavaScript
- less client-side state
- less markup
- less configuration
- less visual noise
If a feature adds complexity, it should earn its place.
## Technical Direction
- Use Razor Pages, not MVC controllers, unless there is a strong reason.
- Prefer static content and server-rendered markup.
- Prefer plain HTML and CSS over client-side frameworks.
- Prefer zero-JS solutions when possible.
- If JavaScript is necessary, keep it small, local, and framework-free.
- Avoid adding databases, auth, APIs, background services, or build tooling unless explicitly needed.
- Avoid third-party frontend libraries by default.
- Keep the solution in `.slnx` format.
## Current Baseline
- .NET 10
- Razor Pages
- Custom CSS in `wwwroot/css/site.css`
- No Bootstrap
- No jQuery
- No README
- GPL license at repo root
## Design Principles
- Clean, calm, and intentional beats flashy.
- Simple typography and spacing are better than heavy UI chrome.
- Content should lead the design.
- Animations should be rare and subtle.
- Mobile and desktop should both feel deliberate.
## Editing Guidance
- Before adding a dependency, ask whether the same outcome can be achieved with HTML, CSS, or Razor alone.
- Before adding a new page model or service, ask whether static markup is enough.
- Before adding configuration, ask whether a hardcoded value is acceptable for a personal site.
- Remove dead files and template leftovers when you see them.
- Keep naming straightforward and boring.
- Favor clarity over cleverness.
## Content and Structure
- Keep page structure shallow and easy to navigate.
- Prefer a small number of well-crafted pages over many thin pages.
- Reuse the shared layout when possible.
- Do not introduce blog, CMS, tagging, search, or feed systems unless explicitly requested.
## Performance
- Keep asset count low.
- Keep CSS lean.
- Avoid shipping large libraries for tiny interactions.
- Favor static assets and built-in ASP.NET Core features.
## Commands
Common verification command:
```bash
dotnet build dwalker.xyz.slnx
```
## Decision Rule
If two approaches are both acceptable, choose the one that is simpler to understand, simpler to maintain, and easier to delete later.
|
