~/ ISMAEL-RAMOS — main · Madrid · Remote
Modern frontend architecture, AI-assisted engineering, performance and user experience.
I'm Ismael — I design and build web systems that stay maintainable as products and teams grow.
LATEST ARTICLE Persisting Windsurf context across sessions with rulesComplex architectural decisions reduced to their measurable outcome. Start with the numbers, then explore the decisions behind them.
Restructuring a long-running frontend around feature boundaries so multiple teams across countries could ship in parallel without stepping on each other.
Designing and shipping Trust·u, a platform that analyzed bank transaction data to generate alternative credit scores for small and medium-sized enterprises — integrating fragmented banking data, complex algorithmic scoring, and bank-grade security into a single unified product.
How a content-heavy scholarship platform moved from inconsistent field metrics to passing CWV thresholds on every monitored route — without dropping the analytics, GTM tags or third-party integrations the business needed.
Work that spans open source contributions and full-stack explorations.
A reference architecture for Angular applications. Patterns for project structure, state and feature boundaries — used as a learning resource by thousands of developers.
An AI-assisted quiz platform for curious minds — turn any topic into a tailored quiz and learn by playing.
A decision-reduction nutrition planner. Built around fast weekly planning and a usability-first interface.
Building systems that remain understandable as they grow — fewer moving parts, sharper boundaries.
Applied in Frontend architecture redesign →Technology decisions should improve user experience and business outcomes, not optimise for the resume.
Applied in Cross-team component library →Fast interfaces shape perception, usability and retention. Speed is a feature, not a polish phase.
Applied in Performance optimisation →Inclusive interfaces are part of good engineering. Semantics and keyboard paths come first, not last.
Applied in Accessibility implementation →Using AI to accelerate execution while keeping engineering judgement and architectural intent.
Applied in AI features integration →Internal tooling, clear conventions and short feedback loops compound product velocity.
Applied in Angular standalone migration →What I'm exploring this quarter alongside the practices that define my work. Both drive the decisions I make.
Where the bulk of my attention is this quarter. Updates with the /now/ page.
↻ updated Apr 12, 2026
The disciplines I bring to anything I build — regardless of stack or quarter.
Architecture
Product engineering
Core technologies
① The shell is the only place routing & auth live — features never reroute themselves.
② Features depend down, never sideways: zero cross-feature imports, lazy by default.
③ The shared kernel is the only thing the platform talks to — swap an adapter, the app does not notice. The diagram is the rule; the rule is enforced by Nx module boundaries.
Articles exploring engineering decisions, architectural patterns, and the craft of building.
A simple Windsurf workflow to carry context across sessions using rules, avoiding token bloat and keeping AI work …
Using Jira and GitHub MCP servers to analyze, classify and plan fixes for PR review comments without leaving the editor.
A small n8n permissions issue reminded me that AI assistants still struggle with niche operational problems where …
Notes on building a tighter feedback loop between PR reviews, Windsurf and the GitHub CLI to make AI-assisted reviews …