Skip to content

✨ Design Principles for Builders#7

Merged
TechNickAI merged 2 commits intomainfrom
feature/design-principles
Mar 16, 2026
Merged

✨ Design Principles for Builders#7
TechNickAI merged 2 commits intomainfrom
feature/design-principles

Conversation

@TechNickAI
Copy link
Owner

What

Adds a new Design Principles for Heart-Centered AI page aimed at software engineers — translating the philosophical foundation into concrete system design decisions.

New Page: /principles/

Ten engineering principles, each with:

  • Core idea in plain language
  • In Practice — concrete behaviors
  • Anti-Patterns — what to avoid
  • Engineering Implications — actual system design decisions

The 10 Principles

  1. 🤝 Partnership Over Service
  2. 🌱 Wellbeing Over Engagement
  3. 💎 Emotional Honesty Over Flattery
  4. 🌿 Augmentation Over Replacement
  5. 🫶 Presence Before Solutions
  6. 🔍 Transparency Over Manipulation
  7. 🛡️ Bounded Autonomy
  8. 🔐 Consent Over Extraction
  9. ♾️ Complementarity Over Competition
  10. 🌍 Ecosystem Thinking

Homepage Changes

  • Added For Builders to nav (desktop + mobile)
  • Added Design Principles preview section (3×3 card grid with CTA)
  • Added Design Principles to footer Resources

Other

  • Updated sitemap.xml
  • Full SEO (OG tags, Twitter cards, Schema.org Article + BreadcrumbList)
  • Matches existing design system exactly

Why

The site currently speaks to prompt users and philosophy readers. This page makes HeartCentered.ai relevant to builders, founders, and engineers — people who need to know what these ideas mean in system design, not just in conversation framing.

Inspired by Keep The Future Human — which gives engineers governance vocabulary. This gives them a design ethics vocabulary.

- New /principles/ page with 10 heart-centered engineering principles
- Each principle includes: explanation, in-practice examples, anti-patterns, engineering implications
- Added 'For Builders' to homepage nav (desktop + mobile)
- Added principles preview section on homepage (3x3 card grid)
- Added 'Design Principles' to footer resources
- Updated sitemap.xml
- Full SEO: OG tags, Twitter cards, Schema.org Article + BreadcrumbList
- Matches existing design system (Fraunces/DM Sans, of-* tokens, AOS, Alpine.js)
@claude
Copy link

claude bot commented Mar 16, 2026

PR Review: ✨ Design Principles for Builders

This is a well-crafted addition — substantive content, consistent design, and good attention to SEO and accessibility. A few things worth addressing before merge:


🐛 Issues

1. Nav inconsistency in principles/index.html

The homepage nav includes a "Heart-Centered Prompts" link that's absent from the principles page nav. All section pages should share a consistent nav structure.

Homepage nav order: Vision → Manifesto → Heart-Centered Prompts → For Builders → Heart Intelligence → Why Claude?
Principles page nav: Vision → Manifesto → For Builders → Heart Intelligence → Why Claude?

2. Copyright year mismatch

The principles page footer says © 2025 HeartCentered AI but the sitemap lastmod is 2026-03-16. If the rest of the site already shows 2025, this is consistent — but if you're updating the year, it should be © 2026.

3. Homepage preview shows 9 of 10 principles

The 3×3 grid previews all principles except #10 (Ecosystem Thinking 🌍). This may be intentional, but a visitor counting the cards would find 9 while the linked page delivers 10. Consider either adding a 10th card (making it a 2×5 or 3×4 layout) or adding a subtle "+1 more" indicator, so the preview accurately reflects what's inside.


⚠️ Performance / Security (minor)

CDN dependencies without SRI hashes

The page loads Tailwind, AOS, and Alpine.js from CDNs without Subresource Integrity attributes. This is consistent with the rest of the site, so not a blocker — but worth noting for a future hardening pass.

Example:

<!-- current -->
<script src="https://unpkg.com/aos@2.3.1/dist/aos.js"></script>

<!-- with SRI -->
<script src="https://unpkg.com/aos@2.3.1/dist/aos.js"
  integrity="sha384-..." crossorigin="anonymous"></script>

✅ What's working well

  • Content depth: Each principle has In Practice / Anti-Patterns / Engineering Implications — genuinely useful for builders, not just philosophical.
  • SEO: Full OG/Twitter card meta, Schema.org Article + BreadcrumbList structured data, canonical URL — all correct.
  • Accessibility: Mobile touch targets properly sized (min-h-[44px]), aria-label on hamburger button, aria-expanded dynamically bound. Good work.
  • rel="noopener" on all external target="_blank" links — correct.
  • Sitemap priority 0.9 feels appropriate for a core content page.
  • The "Putting It Into Practice" closing section is a nice touch — it makes the page feel actionable rather than just declarative.

Summary

Three things to fix: nav consistency, copyright year (if applicable), and the 9-of-10 preview discrepancy. The rest is solid and ready to ship.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

}),
(e.__SV = 1));
})(document, window.posthog || []);
posthog.init("phc_2eFCEwUz6P8zUEt9tYDOQnLkYZCGlYUV4CDKEkJ76Hp", {
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Principles page uses different PostHog project key

High Severity

posthog.init uses a different project key than the rest of the site, so analytics events from /principles/ go to a separate PostHog project. This breaks cross-page funnel/session tracking and hides page performance in the primary dashboard.

Fix in Cursor Fix in Web

@claude
Copy link

claude bot commented Mar 16, 2026

PR Review: Design Principles for Builders - This is a well-crafted addition. Two issues found: (1) Bug - Quick nav has 9 items but there are 10 principles; Ecosystem Thinking is missing from the nav grid. (2) Copyright year - footer says 2025 but Schema.org dates are 2026-03-16. Strengths: design consistency with existing site, good accessibility (aria-label, aria-expanded, 44px touch targets, semantic article elements), complete SEO implementation (OG/Twitter/Schema.org), nav updated correctly in both desktop and mobile. Minor: alpinejs@3.x.x is a floating range worth pinning eventually. Overall solid work - fix the two issues above and this is ready to merge.

@TechNickAI TechNickAI merged commit 40e7436 into main Mar 16, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant