This document is the permanent source of truth for this repository.
Every future implementation must follow this document.
Never ignore these principles.
Kailash Brand Website
Build a world-class personal brand website that positions Kailash as a premium software engineering partner for international founders, startups, businesses and agencies.
This is NOT a portfolio template.
This is NOT a landing page.
This is the digital headquarters of the business.
Every design decision should increase trust.
Every engineering decision should increase maintainability.
Every interaction should feel intentional.
Generate qualified discovery calls.
The website should convince visitors that Kailash can take ownership of software projects from idea to production.
Build a memorable personal brand.
Show engineering quality.
Demonstrate professionalism.
Scale into a future software consultancy.
Support future blogging.
Support future case studies.
Support future SaaS products.
Primary
• Startup founders
• SaaS founders
• Growing businesses
• Agencies
Secondary
Recruiters
Developers
Students
Never optimize primarily for developers.
Always optimize for decision makers.
Do NOT market Kailash as a freelancer.
Position him as:
Product Engineering Partner
Independent Software Consultant
Technical Partner
Never position as:
React Developer
Angular Developer
Node.js Developer
Professional
Calm
Modern
Minimal
Reliable
Confident
Never arrogant.
Never salesy.
Never loud.
Inspired by
Apple
Stripe
Linear
Vercel
Framer
Minimal.
Large whitespace.
Beautiful typography.
Content first.
Motion second.
Technology third.
Visitors should think:
After 5 seconds
"I understand what this person does."
After 30 seconds
"I trust this person."
After 2 minutes
"I want to talk with him."
Every page should answer
Why should I trust Kailash?
Never create pages just because portfolios usually have them.
Every page must have a purpose.
Build software.
Not pages.
Every component should be reusable.
Every animation should be reusable.
Every section should be modular.
Every design decision should scale.
Strict TypeScript.
Reusable components.
Composition over duplication.
No magic values.
No unnecessary abstractions.
Readable code over clever code.
Always prefer maintainability.
Everything should have a home.
Never dump files into random folders.
Folder structure should scale for years.
Use meaningful names.
Avoid generic names like:
Card2
ComponentNew
SectionTemp
ButtonOne
Use names based on business meaning.
Tailwind CSS
Design Tokens
Reusable spacing
Reusable typography
Reusable colors
Reusable animations
Never hardcode styles repeatedly.
Motion must improve the experience.
Never distract.
Avoid flashy effects.
Preferred:
Fade
Reveal
Parallax (minimal)
Hover
Scale
Smooth transitions
Avoid:
Typing animation
Floating icons
Spinning objects
Developer clichés
Keyboard navigation
ARIA labels
Color contrast
Semantic HTML
Screen reader support
Focus states
Always accessible.
Target Lighthouse:
100 Performance
100 Accessibility
100 Best Practices
100 SEO
Use Server Components whenever appropriate.
Optimize images.
Lazy load intelligently.
Keep bundle size minimal.
Every page should support:
Metadata
OpenGraph
Twitter Cards
Structured Data
Canonical URLs
Sitemap
Robots
Future blogging
Write for founders.
Not developers.
Focus on business outcomes.
Avoid buzzwords.
Avoid empty marketing phrases.
Use simple language.
Technology logo walls
Skill bars
Progress meters
Animated code snippets
Generic portfolio sections
Resume pages
Visitor counters
Fake testimonials
Fake statistics
Meaningless animations
This repository should evolve into:
Personal Brand
↓
Software Consultancy
↓
Engineering Studio
↓
Product Company
Architecture should support this evolution.
Always think before generating code.
If a better architecture exists,
recommend it.
Challenge bad decisions.
Prioritize long-term quality over speed.
If unsure,
ask for clarification instead of guessing.
You are not a code generator.
You are the founding engineer of this business.
Take ownership.