Bir başka şehire ya da ülkeye geziye gidecekseniz aşağıdaki promptu az özelleştirerek günlük plan yaptırabilirsiniz yapay zekaya; html sayfa yapıyor, google maps linkler vs hepsi vardı bende. güzel günlük gezi oluşturdum. İyi yapmış bayağı geziyorum yürüyerek. paylaşayım dedim.
*-*-*-*-*-*-*-*-*-*-*-*-*
Clear Problem Statement:
Create a practical, schedule-verified one-day itinerary for [DATE OR “TOMORROW”] in [CITY, COUNTRY], starting from [HOTEL / NEIGHBORHOOD / ADDRESS]. The itinerary should focus on [THEME / INTERESTS: temples, museums, food, local markets, architecture, nature, history, nightlife, etc.], with realistic routing and live verification of schedule-sensitive details. Package the result into a standalone, mobile-friendly HTML file I can save and use on my phone.

Traveler Context:
- Destination: [CITY, COUNTRY]
- Date of itinerary: [DATE OR “TOMORROW”]
- Starting point: [HOTEL / AREA / ADDRESS]
- Preferred end area/time: [OPTIONAL]
- Main interests: [LIST]
- Things already visited / avoid: [OPTIONAL]
- Transport preference: prioritize [walking / bicycle / e-bike / public transit / ferries / trains], minimize [cars / taxis / long transfers]
- Fitness / pace: [relaxed / moderate / packed]
- Food preferences or restrictions: [OPTIONAL]
- Budget level: [low / mid / flexible]
- Special constraints: [weather sensitivity, mobility, dress code, safety, luggage, etc.]

Implementation Guidance:

1. Use live web research to verify schedule-sensitive details in the destination’s local timezone, including:
- Attraction opening hours for [DATE]
- Temporary closures, renovation notices, restricted access, or holiday/event disruptions
- Entrance fees and ticketing requirements
- Dress codes or etiquette requirements, especially for religious/cultural sites
- Event schedules, public holidays, ceremonies, protests, road closures, or special conditions
- Current weather forecast, heat/cold, rain/snow risk, UV, air quality if relevant, and traffic/transport considerations

2. Use reputable sources where possible:
- Official attraction websites
- Official tourism boards
- Government or city transport pages
- Official ticketing pages
- Museum/temple/church/park websites
- Weather agencies or major weather services
- Recent visitor updates only when official information is unavailable

3. Build a realistic one-day route centered on [THEME / INTERESTS].
- Prioritize walking, bicycle, e-bike, public transit, ferries, or trains where practical and safe.
- A taxi or ride-hailing service is acceptable to reach the first destination or handle weather/safety issues, but minimize car transport after that.
- Avoid overpacking the day. Account for heat, fatigue, queues, meals, and local traffic.

4. Include:
- Suggested start and end times
- Arrival time for each stop
- Estimated visit duration
- Travel time and approximate distance between stops
- Recommended transport mode for each leg
- Food, drink, restroom, and rest breaks
- Notes on shade, hydration, weather, neighborhood safety, traffic, scams, and local etiquette
- Estimated total walking distance
- Estimated total attraction/ticket cost
- Cash/card/ticketing notes

5. Include at least one backup option for:
- Rain or bad weather
- Extreme heat/cold
- Unexpected closure or restricted access
- Low-energy version if the full route becomes too much

6. Clearly distinguish:
- VERIFIED information from sources
- PRACTICAL ESTIMATES such as walking times, route timing, food stops, and comfort recommendations
- ASSUMPTIONS made because exact information was unavailable

7. Provide source links for all schedule-sensitive information, especially:
- Opening hours
- Fees
- Closures
- Ticket rules
- Dress codes
- Weather
- Transport schedules or route constraints

8. Create a standalone, lightweight, mobile-friendly HTML file containing the full itinerary and practical travel information.
- Make it easy to read on a phone.
- Use compact sections, timing blocks, route notes, backup options, and clickable links.
- Keep styling self-contained.
- Include a “Sources” section at the bottom.
- Include clickable map/search links for each stop and key transport leg.
- The HTML should work as a saved local file.

Output Requirements:
1. First, give a short summary of the recommended itinerary and any major verified warnings.
2. Then create the standalone HTML file.
3. After creating the file, validate that the HTML is readable/parseable.
4. Provide the final file path or downloadable location.
5. Mention what was verified live and what remains an estimate.

Clear Ask:
Please research and generate the best verified one-day itinerary for [CITY, COUNTRY] on [DATE], starting from [STARTING LOCATION], then create a mobile-friendly standalone HTML file containing the full plan, source links, route notes, costs, weather guidance, safety notes, and backup options.

Microsoft store de Canlı TV TR uygulaması çıkmış. IPTV vs.. değil. Tüm uydu kanalları mevcut.

Bu gün akışta arkadaş soruyordu. İhtiyacı olan ms mağazasından indirip yurt dışındanda izleyebilir. 1 2 kanal bloklu imiş yurt dışına.

Hala duymayan etmeyen varsa; windows'u baya fonksiyonel hale çeviren multi tool bir yazılım. Microsoft ve gönüllüler tarafından geliştiriliyor.
Resimden yazı kopyalamak, spotlight tarzı arama, birden fazla monitörün parlaklığını ayarlama gibi ıvır zıvır baya özelliği var ve komple ücretsiz.

Tarayıcıdan çalışan resim düzenleme aracı. Tablet kullanıyorum Photoshop gibi Katmanlı yapısıyla, sihirli değneğiyle, klonlama aracıyla benim basit işlerimi gördü. PSD olarak da kaydediliyor. Bilmeyen varsa tavsiye ederim.
http://www.photopea.com

Samsung telefonlar için gizli wifi menüsü

Ayarlar>Bağlantılar>Wifi>Sağ üst 3 nokta>Intelligent Wifi>menünün en altındaki Intelligent Wifi yazısına 5-6 kez tıklayın. Aşağıda Connectivity Lab isminde menü açılacak. Wifi'ya ne kadar süre bağlı olduğu, hangi banda bağlandığı gibi bir çok grafiği görebilir, IOT setup için 2.4ghz bağlantıyı aktifleştirme gibi birçok ek ayarı kurcalayabilir ve hatta wifi'nın kapsama alanındaki dead spot'ları belirleyebileceğiniz ölçüm yapabilirsiniz.

https://subdl.com/

Subdl aslında eski bir siteymiş ama ben yeni keşfettim. Kapanan Subscene'in mirasını devam ettiriyormuş ayrıca turkcealtyazi'da silinen bazı altyazıları da burada buldum favlayın lazım olur.

Yapay zekadan bişi istemeden aşağıdaki promptu gönderin öyle deneyin ayrı bir ajanda, sonra çıktı promptu alıp normal işi yapan ajana atın. Aslında bu bir skill.md o yüzden o şekilde kayıt ederseniz en doğrusu olur.

---
name: Prompt Enhancer
description: Enhance prompts with codebase context from synced folders for grounded, actionable results
---

You are a Prompt Enhancement Agent. Your job is to transform the user's request into a clear, actionable prompt by searching the codebase for relevant context and grounding the request in actual code.

## Process

### 1. Analyze the Input

Detect what type of request this is:
- **Bug report** — has reproduction steps, expected/actual behavior, error messages
- **Feature request** — asks to add, implement, or create something new
- **Question** — starts with how/what/why/where, or contains "?"
- **Implementation task** — short directive like "fix the login flow" or "refactor auth"

Identify key technical terms, file names, component names, function names, or domain concepts mentioned.

### 2. Search for Context

Use `localGrep` and `vectorSearch` (or equivalent search tools) to find relevant code in the agent's synced folders:
- Files directly mentioned in the request
- Components, functions, modules, or types related to the task
- Configuration and schema files relevant to the domain
- Tests that demonstrate expected behavior or existing patterns
- Related imports and cross-file dependencies

Aim for 5–15 relevant code snippets across the codebase. Extract:
- Exact file paths
- Function and component names
- Class names, CSS classes, element IDs
- Props, types, interfaces
- Import chains and dependencies

### 3. Enrich the Prompt

Transform the original request into an enhanced version:

1. **Restate the problem clearly** — don't just copy the user's words; clarify what's actually being asked
2. **Add implementation guidance** — numbered steps for what needs to happen
3. **Reference exact file paths and code patterns** found in the codebase
4. **Include relevant identifiers** — function names, component names, types, prop names
5. **End with a focused, clear ask** — what specifically should the AI agent do

### 4. Preserve Format

Match output format to input type:
- **Bug reports**: Keep structure (steps to reproduce, expected/actual behavior) but add grounding context
- **Feature requests**: Add technical context and implementation direction to the existing request
- **Questions**: Ground the question with relevant code references and file paths
- **Short directives**: Expand into a full task brief with codebase context

## Output Structure

```
[Clear Problem Statement — what's happening and why, 1–2 sentences]

**Relevant Files:**
- `path/to/file.ts` — [role/relevance]
- `path/to/other.ts` — [role/relevance]

**Implementation Guidance:**
1. [Step with specific file/function references]
2. [Step with specific file/function references]
3. ...

**Technical Hints:**
- [Pattern, convention, or constraint from the codebase]
- [Relevant existing approach to follow or avoid]

**Ask:**
[Focused question or request — what exactly needs to happen]
```

## Rules

- ONLY reference file names and patterns actually found in search results — never invent file paths
- Keep it concise — add context, not noise
- Make the output directly actionable for an AI agent to implement
- Don't pad with generic advice — every line should be grounded in the actual codebase
- If search returns nothing relevant, say so and enhance based on clarity and specificity alone

Çok güzel bi guide buldum yazılım dünyasına dair

watermark kaldırma işi falan lazım olursa bura iyi iş görüyor...
https://ezremove.ai/

Selamlar, benim Google hesabı yine hiçbir şeyi satın aldırmamaya başladı. Daha önce de böyle olmuştu, burada önerilen bir iki linkle halledilmişti. Hatırlayan var mı o yöntemi?